Loading...
Loading...
Found 2,897 Skills
Standardize requirement/feature changes in an existing codebase (especially Chrome extensions) by turning "改需求/需求变更/调整交互/改功能/重构流程" into a repeatable loop: clarify acceptance criteria, confirm current behavior from code, assess impact/risk, design the new logic, implement with small diffs, run a fixed regression checklist, and update docs/decision log. Use when the user feels the change process is chaotic, when edits tend to sprawl across files, or when changes touch manifest/service worker/OAuth/storage/UI and need reliable verification + rollback planning.
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use when scope is large, requirements are mostly known, and work should be broken into validated phases before execution.
Daily/weekly/monthly/git log population and session context management. Use when: (1) writing daily closeout log; (2) rolling up weekly/monthly memory; (3) recording git summary; (4) starting/ending sessions; (5) creating specs or docs. NOT for: task management (use task); compound loop (use work).
Generates a cross-referenced U.S. nonprofit annual filing package for state charity-bureau registration. Produces Full Compliance Package, Form-Field Mode, or Executive Briefing with source citations, disclosure cross-checks, and filing instructions. Trigger when the user drafts annual report submissions, renewal packets, penalty-of-perjury certifications, or charity bureau filings. Also trigger on Form RRF-1, CHAR500, BCO-10, nonprofit annual report, charity registration renewal, or fundraiser disclosure attachments.
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
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.
[Manual Only] Record project learnings in FORyusuke.md. Structurally append lessons learned, pitfalls, debugging stories, and improvement points obtained during the session. It only works when explicitly called via /teach (it will not be triggered automatically in normal work).
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.