Loading...
Loading...
Found 863 Skills
Writing one Epic's spec.md by synthesising the scoping session that just happened, asking nothing. Reached by /archie-architect when a scoped Epic has no Spec, or when the call on an Epic is specify.
Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.
Use when adding, editing or reviewing skills, role prompts or skill metadata.
Creates Source-of-Truth docs (Project Brief, Decisions, Glossary) for new app ideas. Use at the very start of a project to lock scope, stack, and terminology. Essential for preventing drift in downstream PRD, UI/UX, and Architecture phases.
Complete spec workflow - generates Run ID, creates isolated worktree, brainstorms requirements, writes lean spec documents that reference constitutions, validates architecture quality, and reports completion
Turn a chosen segment + Core Jobs into a build-ready PRD (full functionality + edge cases) using Ivan Zamesin's AJTBD / Next Move Theory methodology. It consumes upstream work — segments from /nmt-market-research, value from /nmt-craft-value-proposition — and never re-derives them; with no research done it routes you upstream first, or takes a manually described segment + value for a fast run. Before writing requirements it runs a "challenge the build" gate that looks for a more effective way to hit the same business goal; if a better way wins, the PRD is written for that. Output — a single PRD — functionality mapped Core Job → Big Job → value mechanic → success criteria → Aha Moment on the Critical Chain of Jobs, plus edge cases covering ~90% of use cases. Use when the user says "write the PRD / product requirements" or wants to turn a segment+value or a feature idea into a build spec. Two modes — Quick (default, no internet) and Deep (subagents + web parity check). Plain language; defaults to English.
契約による設計で、自然言語要件を事前条件・事後条件・不変条件・失敗保証・冪等性・契約テスト仕様へ変換するときに使う。一般的なテスト追加、UI入力検証だけ、統合実装全体には使わない。
Design a UI component spec to the house quality bar — anatomy, variants, sizes, the 8 states, token mapping, and accessibility. Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework code, use design-code.
REST and GraphQL API design best practices including OpenAPI specs. Use when designing APIs, documenting endpoints, or reviewing API architecture.
Evidence-grounded legacy-repository understanding with recurrent human feedback and bounded skill convergence. Activates when the user asks to understand, map, document, onboard to, refactor, modify, or assess a repository.
Reference for any XRPL Standard (XLS-N) when implementing or reviewing XRPL protocol features. Trigger on: XLS number (XLS-30, XLS-70), amendment name (AMM, Credentials, MPT, DID, NFToken, Batch, Escrow, Clawback, Firewall, Permissioned DEX), transaction type (AMMCreate, CredentialCreate, NFTokenMint, DelegateSet, PermissionedDomainSet, BatchSubmit), or ledger object name (Credential, AMM, MPToken, Delegate, Oracle, Bridge).
Activate for business cards, flyers, invitations, packaging, posters, and any physical media design.