agentleFS
ea-toolkitea-toolkit/architecture-catalog/.claude/skills/new-entry/SKILL.md

new-entry

Skill38 starsChanged 9 months agoMITView on GitHub

Create a new registry entry with guided wizard. Supports components, data-objects, functions, services, and other ArchiMate element types.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If arguments not provided, ask the user:

    line 18
  2. Distinctive:

    Do NOT hardcode paths: Always discover dynamically:

    line 25
  3. Very specific:

    Use the folder: field for that type to determine the target directory

    line 29
  4. Very specific:

    Read _template.md in the target folder for structure

    line 37
  5. Distinctive:

    Read 1-2 existing entries in target folder for pattern reference

    line 38
  6. Distinctive:

    Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")

    line 39
  7. Distinctive:

    Write file to correct folder

    line 45
  8. Distinctive:

    Always use kebab-case for filenames

    line 83
  9. Distinctive:

    Run validation after creation to catch issues early

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Create New Registry Entry

Guide the user through creating a properly structured registry entry.

Arguments

  • $1 - Element type: component, software-system, data-concept, data-aggregate, data-entity, domain-event, api-endpoint, etc.
  • $2+ - Element name (can have spaces)

If arguments not provided, ask the user:

  1. What type of element?
  2. What is the element name?
  3. Which domain does it belong to?

Element Type to Folder Mapping

Do NOT hardcode paths. Always discover dynamically:

  1. Read models/registry-mapping.yaml
  2. Find the element type under elements:
  3. Use the folder: field for that type to determine the target directory
  4. Prepend registry-v2/ to the folder path

This ensures the skill works even if users rename layers, types, or restructure folders.

Workflow

  1. Determine element type and target folder
  2. Read _template.md in the target folder for structure
  3. Read 1-2 existing entries in target folder for pattern reference
  4. Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")
  5. Fill frontmatter:
    • name: [provided name]
    • owner: TBD
    • status: draft
    • [type-specific fields and relationships from template]
  6. Write file to correct folder
  7. Run validation: python scripts/validate.py

Response Format

**Created:** registry-v2/<layer>/<type-folder>/element-name.md

**Frontmatter:**
---
type: <element-type>
name: <Element Name>
owner: TBD
status: draft
<type-specific fields from template>
---

**Next Steps:**
1. Fill in TBD fields
2. Add description in the body
3. Run /validate to verify

Would you like me to help fill in any of the TBD fields?

Domain-Specific Fields

For data elements (concepts, aggregates, entities), also include:

  • Relationship to parent element (data concept -> aggregate -> entity chain)
  • classification: internal/business-confidential/pii

For software elements (systems, subsystems), also include:

  • sourcing: in-house/vendor/hybrid
  • vendor: (if vendor)
  • realizes_component: Which component this system supports

Notes

  • Always use kebab-case for filenames
  • Mark unknown fields as TBD rather than guessing
  • Run validation after creation to catch issues early
  • Suggest wiring relationships as a follow-up action

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.