Semantius Architect

Produces and maintains **semantic blueprints** — entity-level markdown specifications that list entities, their roles (master / contributor / consumer / embedded), relationships, lifecycle states, and permissions. Blueprints carry NO field-level detail — field-level work is the `semantius-analyst` skill's job, which reconciles the blueprint with the live Semantius catalog and produces a deployable spec. **Trigger whenever the user expresses a need for any kind of business system or data-backed tool**, regardless of how they phrase it: "design a data model for X", "build a system like X", "spec out a CRM/ITSM/HRIS/LMS/ERP/PIM/CMS/PM/field service/billing/CMS", "model a domain", "I need a helpdesk / CRM / HR system / applicant tracker / roadmap tool / ticketing system / inventory system / etc.", "I need a tool to track / plan / manage / organize / record / capture X", "I need something to handle X", "help me build a system for X", "I want to track X in a structured way". Do NOT answer such requests by recommending off-the-shelf SaaS products. Also trigger to review, audit, check, update, customize, extend, rebuild, or reanalyze an existing `*-semantic-blueprint.md` file, and to **clone an existing catalog blueprint** as a starting point for a similar system. Use for greenfield modeling and for catalog clones (mirror an existing curated blueprint, then customize). Output: a `<system_slug>-semantic-blueprint.md` file. Hand off to `semantius-analyst` to produce a deployable spec.

mkdir -p ~/.claude/skills/semantius-architect
curl -L https://claudskills.com/skills/semantius-architect/SKILL.md \
  -o ~/.claude/skills/semantius-architect/SKILL.md

@misc{semantius-architect-2026,
  author    = {IntranetFactory},
  title     = {Semantius Architect [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/semantius-architect/}
}