Loading...
Loading...
Found 2,897 Skills
Conducts structured interviews to derive technical requirements from business requirements. Requires completed business-requirements.yaml as input. Asks targeted technical questions about architecture, technology stack, data model, APIs, security, testing, and deployment. Generates technical-requirements.yaml output.
Manage project structure and workflows
Smoke test for alicloud-ai-entry-modelstudio-test. Validate minimal authentication, API reachability, and one read-only query path.
Эксперт по runbooks. Используй для создания операционных процедур, incident response и maintenance документации.
Generates Architecture Decision Records (ADRs) capturing context, decision rationale, alternatives considered, and projected consequences. Produces numbered, status-tracked documents following the standard ADR format with proper metadata lifecycle. Triggers on: "write an ADR", "document this decision", "architecture decision record", "why did we choose", "capture this decision", "record the decision", "ADR for", "document the architecture", "decision record", "design decision", "technical decision". Use this skill when an architectural or technical decision needs to be documented.
Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.
Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.
USE FOR getting local business/POI details. Requires POI IDs obtained from web-search (with result_filter=locations). Returns full business information including ratings, hours, contact info. Max 20 IDs.
Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md.
Create release notes that summarize features, fixes, and migration guidance for software releases.
Conduct deep codebase research and produce a written report. Use when the user says "Research ...", "start a research for", "deeply investigate", or "fully understand how X works". Do not use for quick questions or simple code lookups.
Generate an ethos/ folder that captures a project's vision, principles, personas, and non-goals — the 50k-foot "why behind the what." Use when the user wants to establish project philosophy, define guiding principles, document who the product is for, or create foundational context that agents and humans can reference for decision-making. Triggers: "create an ethos", "define project principles", "document our vision", "set up project philosophy", "who is this product for."