Menu
Design the generation pipeline for non-text deliverables — templates, rendering, design tokens, storage, and verification.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Audit a generated OS repository for completeness, consistency, and architectural integrity against the 15 design principles and 23-item checklist.
Transplant a skill, command, or capability from one agentic-system repo into another via a 5-phase gated protocol (inventory → import → localize → wire → verify). Use when grafting a feature from an upstream repo that has its own dependencies, platform assumptions, or upstream-specific file references that need adapting before the feature will work in the destination repo. Not for copying a self-contained file — use only when the feature has a dependency footprint and the destination repo has its own conventions the import must respect.
Design multi-dimensional evaluation rubrics with calibrated scales, thresholds, and function-adaptive weights.
Identify who evaluates the user's output, what each audience prioritizes, and where their priorities conflict.
Define the user context model — identity axes, context files, persona variants, and privacy rules for the target OS.
Design compounding feedback loops — what data accumulates, what reads it, and how the system gets smarter with use.
| name | design-artifact-pipeline |
| description | Design the generation pipeline for non-text deliverables — templates, rendering, design tokens, storage, and verification. |
/design-skills (need to know which skills produce artifacts)domain-input/artifact-pipeline.md needs to be filledoutput/designs/skill-designs.md (which skills produce non-text output)domain-input/audiences.md (who receives artifacts, what format they expect)domain-input/domain-workflow.md (where artifacts fit in the pipeline)From the skill designs, list every non-text output:
| Artifact Type | Produced By | Format | Audience | Purpose |
|---|---|---|---|---|
| [e.g., Tailored resume] | /[skill] | Recruiter, ATS | Job application | |
| [e.g., Evaluation report] | /[skill] | Markdown | User | Decision support |
| [e.g., Data export] | /[skill] | CSV/TSV | External system | Data transfer |
For each artifact type with a non-trivial render process:
Template:
Design Tokens (for visual artifacts):
Content Generation:
Render Pipeline:
Tool Requirements:
Storage & Naming:
Verification:
If multiple artifacts share visual design:
For each render tool dependency:
Write the artifact pipeline specification to domain-input/artifact-pipeline.md.
Tell the designer:
Artifact pipelines designed:
- [N] artifact types: [list]
- Render tools required: [list]
- Design tokens: [centralized / per-artifact / not applicable]
- Fallback behavior: defined for all tool dependencies
Next: Run /design-batch-architecture if the OS needs scale processing.
Or skip to /generate-os.
Good artifact pipeline:
Bad artifact pipeline: