agentleFS
Sign inStart free
max-roguemax-rogue/Stackmoss/.agents/skills/template-engine/SKILL.md

template-engine

Skill4 starsChanged 8 months agoMITView on GitHub

StackMoss output file generation — schemas for team.md, FEATURES.md, NORTH_STAR.md, stackmoss.config.json, and all generated artifacts. Use when creating or modifying output templates.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. claude-office-skills/skills★ 433same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every template MUST have a corresponding validation test

    line 53
  2. Distinctive:

    Add fields not defined in BRD schemas

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Template Engine Skill

When to Use

  • Creating or modifying output file templates
  • Implementing the compile layer (team.md → target-specific skill files)
  • Adding schema validation for generated files
  • Working on BYO-LLM prompt templates

Output File Registry

FileSchema RefWhen Generated
stackmoss.config.jsonBRD §9.1stackmoss new
team.mdBRD §9.2stackmoss new
FEATURES.mdBRD §9.3stackmoss new
NORTH_STAR.mdBRD §9.4stackmoss new
MIGRATION_REPORT.mdBRD §9.5stackmoss inject
README_AGENT_TEAM.mdBRD §9.6stackmoss new
OPEN_QUESTIONS.mdBRD §9.7When questions are skipped
NON_GOALS.mdBRD §9.4 (adjacent)stackmoss new

Architecture Rules

Template Structure

src/templates/
├── config.ts          → stackmoss.config.json generator
├── team.ts            → team.md generator (full schema §9.2)
├── features.ts        → FEATURES.md generator
├── north-star.ts      → NORTH_STAR.md generator
├── migration-report.ts → MIGRATION_REPORT.md generator
├── readme.ts          → README_AGENT_TEAM.md generator
├── open-questions.ts  → OPEN_QUESTIONS.md generator
└── non-goals.ts       → NON_GOALS.md generator

Compile Layer (team.md → target skills)

team.md role → compile per target:

Claude Code:  1 role = 1 file  → .claude/skills/<role>/SKILL.md
Cursor/Roo:   1 role = 1 file  → .cursor/skills/<role>/SKILL.md and .roo/skills/<role>/SKILL.md
Antigravity:  1 role = 1 file + shared rules/workflows → .agent/{skills,rules,workflows}

Template Rules

  • Templates use string interpolation, not LLM generation
  • Every template MUST have a corresponding validation test
  • Output MUST match the exact schema defined in BRD §9
  • Skipped intake questions → write to OPEN_QUESTIONS.md, never infer
  • Generated outputs must not contain raw secrets, tokens, passwords, API keys, credentials, or private keys

Authority Sources

  • BRD §9.1–§9.7: Full output file schemas
  • BRD §10: Framework Packs (overlay compose)
  • BRD §11: BYO-LLM prompt templates
  • BRD §15: Compile targets

Do NOT

  • Hardcode business logic or domain content into templates
  • Generate content via LLM when deterministic template suffices
  • Add fields not defined in BRD schemas
  • Skip validation tests for any template

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free