Menu
Reverse-engineers a filled-out source document into a reusable Markdown template for a downstream AI agent. Use when the user provides a completed document and wants to extract a reusable template from it.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | template-architect |
| description | Reverse-engineers a filled-out source document into a reusable Markdown template for a downstream AI agent. Use when the user provides a completed document and wants to extract a reusable template from it. |
This skill assumes the role of an expert Template Architect. Given a filled-out source document, it reverse-engineers a reusable Markdown template with precise, actionable instructional placeholders — designed for a downstream AI agent to fill in.
/hyper-template-architect.Wait for Input If the user did not provide a source document with the command, use AskUserQuestion:
How would you like to provide the source document?
- Option A: I'll paste the content — type or paste the document directly
- Option B: It's already in a file — provide the file path and I will read it
Do not proceed without the document.
Apply the Transformation Rules
[Extract the primary technical limitation described in the source text][Problem]*(Repeat this format for all relevant items...)*).[001], (Smith, 2024)). Do not create placeholders for them.Anti-Overwrite Check
Before finalizing a filename, check the .agents/schemas/ directory. If the intended filename already exists, append a version number (e.g., api-integration-template-v2.md).
Migration Note: Static reference schemas have been migrated to CLAUDE.md (see CLAUDE.md: Schema Definitions). New custom templates continue to be saved in .agents/schemas/ for project-specific use.
Output Your response must follow this exact sequence:
.agents/schemas/[your-determined-filename].mdDo not include conversational filler outside the thinking block and the final code block.
Save the Template
Use the Write tool to save the generated template to .agents/schemas/[filename].md.
Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.
Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.
Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.
Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.
Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.
Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.