meta-concept-contract
contractShared contract for multi-product umbrella concepts. Defines the _concept/ structure for projects composed of multiple independent subsystems, each with its own codebase, tech stack, and deployment model.
11 assets
Shared contract for multi-product umbrella concepts. Defines the _concept/ structure for projects composed of multiple independent subsystems, each with its own codebase, tech stack, and deployment model.
Shared contract for all knowledge-research skills. Describes research output folder structure, findings format, citation conventions, and how research artifacts are consumed by downstream skills.
Shared contract for all knowledge-writing skills. Describes writing output formats, chapter/episode structure, template conventions, and how writing skills consume research artifacts.
Shared contract for all JavaScript/TypeScript implementation expert skills. Describes the expert skill folder structure (recipes, atomic-examples, reference-implementations), discovery conventions, and how experts are consumed by implementation skills.
Shared contract for all use-* integration skills. Describes integration skill conventions, API key handling patterns, MCP vs direct-API usage, output format, and how use skills are composed with other skills.
Shared contract for all impl-build-implementation skills. Describes _implementation/ folder layout, scaffold-to-verify pipeline, progress.json format, git workflow, and how implementation reads from _concept/. REQUIRED reading for any implementation skill.
Shared contract for all Python implementation expert skills. Describes the expert skill folder structure, discovery conventions, and how Python experts are consumed by implementation skills.
Shared contract for all impl-quality skills. Describes quality report formats, score schema, audit output structure, test file conventions, and cross-reference integrity rules.
Shared contract for all impl-architecture skills. Describes _standards/ folder layout, profile format, standards injection protocol, and how profiles map to tech-stack choices.
Shared contract for all skaileup-conceptualization skills. Describes _concept/ folder layout, skill naming conventions, pipeline phase structure, and file ownership rules. REQUIRED reading for any cf_* or saxe_* conceptualization skill.
Shared contract for all skill-builder domain skills. Describes skill folder structure, SKILL.md frontmatter conventions, CLI.md format, progressive disclosure loading strategy, and how skill-builder skills are composed. REQUIRED reading for skills that create or scaffold other skills.