New entry

Skill ea-toolkit/architecture-catalog/.claude/skills/new-entry

Git-native architecture catalog — Markdown registry, schema-driven UI, AI-ready

Install

npx -y skills add ea-toolkit/architecture-catalog --skill new-entry

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.5 KB, as published. Nobody here has run it

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:

What type of element?
What is the element name?
Which domain does it belong to?

Element Type to Folder Mapping

Do NOT hardcode paths. Always discover dynamically:

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

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

Workflow

Determine element type and target folder
Read _template.md in the target folder for structure
Read 1-2 existing entries in target folder for pattern reference
Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")
Fill frontmatter:
- name: [provided name]
- owner: TBD
- status: draft
- [type-specific fields and relationships from template]
Write file to correct folder
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