NekoCore-OS blueprint-builder
Create and register new MA task blueprints, task types, and classification rules
git clone https://github.com/voardwalker-code/NekoCore-OS
T=$(mktemp -d) && git clone --depth=1 https://github.com/voardwalker-code/NekoCore-OS "$T" && mkdir -p ~/.claude/skills && cp -r "$T/project/MA/MA-skills/blueprint-builder" ~/.claude/skills/voardwalker-code-nekocore-os-blueprint-builder && rm -rf "$T"
project/MA/MA-skills/blueprint-builder/SKILL.mdBlueprint Builder Skill
Triggers
- "create a blueprint", "build a blueprint", "make a blueprint"
- "design a blueprint", "write a blueprint", "new blueprint"
- "blueprint for X", "need a blueprint for X"
- "there's no blueprint for X", "missing blueprint"
- "create a task type", "new task type", "add a task type"
- "create a workflow", "build a workflow"
- "teach MA how to do X"
Workflow
-
Capability Analysis — Understand what the user wants MA to be able to do. Extract: task description, inputs needed, outputs produced, whether entity creation / web research / multi-mode is needed. Check existing blueprints for overlap.
-
Blueprint Design — Design the structure: modes (if multi-modal), phases per mode, interactive pauses, output format, tool calls needed. Follow mandatory conventions:
- Header → Goal → Mode Detection → Architecture → Step Pattern → Phases → Guidelines
- 150-400 lines target
- Explicit tool call syntax in every phase
- DO/DON'T guidelines specific to this task type
-
Write Blueprint — Write
with full production-quality blueprint.MA-blueprints/modules/{task_type}.md -
Write Skill Files — Write
(YAML frontmatter + triggers + workflow + tools) andMA-skills/{skill-name}/SKILL.md
(compact runtime reference, under 80 lines).MA-entity/entity_ma/skills/{skill-name}.md -
Generate Classifier — Generate the exact TASK_TYPES, COMPLEX_TASK_TYPES, and RULES entries for MA-tasks.js. Write to a registration summary file with verification instructions.
-
Summary — Present: files created, registration snippet, test commands, capability description.
Quality Standards
- Blueprint must be self-contained — executable by an LLM with no external context
- Every phase needs concrete tool call examples
- Keywords designed to avoid collision with existing 17 task types
- Mode detection tables include ASK fallback for ambiguity
- Output always goes to workspace files, not chat
Tools Used
— Check existing blueprints for overlapws_list
— Read existing blueprints for pattern referencews_read
— Write blueprint, skill, and summary filesws_write