Optional using-loom-design discovery routing and two stations — capture-intent, write-spec — turn a rough idea into a confirmed intent and a risk-declared spec, route non-blocking second-vendor suggestions, and provide product-principles, design-system, architecture-design and design-research tools. Claude Code, Codex + Antigravity CLI.
Plugin loom-design from marketplace loom in kouko/loom-plugins. Commands read from the repo's manifest — today.
architecture-designDesign and ratify ARCHITECTURE.md with the user: module boundaries, tech choices, folder layout, CI stages, then guard tests. Use to design or change a project's architecture. 架構設計 / 架構規則 / アーキテクチャ設計.
capture-intentCapture and confirm a change intent. Use for any software request to add a feature or fix a bug, before editing files, even when loom is not named or the repo has no loom folder. Skip a typo or a rename that changes no behaviour (unless loom is asked for), skip non-software work, and skip a request
design-researchResolve consequential evidence gaps about user problems, usage context, outcome priorities, behavior alternatives or architecture decisions. Return bounded findings to the design task; adequate evidence needs no new study.
design-systemRatify a visual DESIGN.md. Use for a UI design system: colors, type, layout, and component tokens. 視覺設計系統 / デザインシステム.
product-principlesRatify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.
using-loom-designRoute Loom product-definition requests to intent, specification, principles, visual design, architecture or design research skills when the needed skill is unclear.
write-specWrite a design spec from a confirmed intent. Use for a requested spec or a needs-design: yes intent without one.
Optional using-loom-workflow discovery routing and Loom workflow tools around the loom stations — persistent Outcome Maps, git memory, loom-memory (recall / record / reconcile / retire durable repository lessons), critique (proposal | complexity), recap, handoff, project-retro and skill-retro, CoT explainers, cross-executor second opinion, plus the standalone goal-create and dbt-model-style skills.
14 skills · hooks
Optional using-loom-code discovery routing and five stations carry one change from plan to PR with non-blocking cross-vendor suggestions, content-bound verification, one closing review, and a GitHub-enforced PR floor. On-demand engineering research resolves decision-critical evidence gaps. Claude Code, Codex + Antigravity CLI.
7 skills · 4 agents · hooks
Spec Driven — orchestrator-first Agent Skills for spec-driven development. The orchestrator skill turns a PRD or idea into approved SPECs, tracked GitHub Issues, TDD-implemented slices, QA gates, and reviewed PRs. Includes gap-analysis, write-specs, execute-specs, scaffold-mvp, create-issues, qa-analyst, code-review-and-quality, sonarqube-autofix, draw.io/Mermaid architecture diagrams, and MCP integrations.
27 skills · 27 commands · 8 MCP servers
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.