How do I install the Project Architecture skill?

Run npx skillmds@latest add telum-ai/project-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Architecture?

telum-ai (@telum-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Architecture by telum-ai — Agent Skill

Name: Project Architecture
Rating: 4.2 (5 reviews)
Author: telum-ai

File contents

project-architecture

Input: $ARGUMENTS (focus areas, constraints). Output: [PROJECT_DIR]/architecture.md. Template: .speck/templates/project/architecture-template.md. Prereq: project.md, context.md (REQUIRED). Runs before /project-plan.

0. Template

Read .speck/templates/project/architecture-template.md before writing.

1. Play level

Read .speck/project.json → play_level.

Level	Action
Sprint	STOP — skip formal architecture; `/project-promote` when ready
Build	Optional — proceed only if user confirms or tech uncertain
Platform	Full flow

2. Load context

project.md, context.md (STOP if missing → /project-context)
constitution.md, ux-strategy.md, *-research-report-*.md
Brownfield: project-landscape-overview.md, project-import.md
Recipe: _active_recipe: → .speck/recipes/[name]/recipe.yaml (stack, architecture, patterns, external_services)

Mode: landscape exists → brownfield (as-is + to-be); else greenfield.

3. JIT research

Follow .cursor/skills/just-in-time-research/SKILL.md. Gap areas: stack evaluation, patterns, performance, integration, migration (brownfield).

Deep research needed → PAUSE: project-architecture-research-prompt-[topic].md → user saves project-architecture-research-report-[topic].md → re-run.

4. Brownfield

Extract from landscape: pattern, components, stack, data models, APIs, deployment, debt. Document current state; propose evolution aligned with context.md constraints.

5. Greenfield

Decide: pattern, deployment targets, quality attributes, frontend/backend/DB/integration choices. Verify against context.md (team skills, infra limits).

Recipe active → pre-fill from recipe; ask only gaps.

6. Write architecture.md

Fill template. Include: components, stack rationale, data/security/performance/scaling/integration/deployment/ops. ASCII or Mermaid diagrams. Cross-reference epic boundaries and shared components.

Embed research in "Research Informing This Architecture."

7. Validation checklist

Supports functional + non-functional reqs; fits constraints; clear epic boundaries; independent epic development; security + scale addressed.

8. Next

Step	Notes
`/project-design-system`	UI-heavy projects
`/project-plan`	Consumes architecture.md
`/project-validate`	Post-implementation only

NEVER / ALWAYS

NEVER plan Platform without architecture feeding /project-plan
NEVER contradict context.md constraints silently
NEVER skip as-is documentation in brownfield
ALWAYS read template first
ALWAYS document trade-offs and evolution path

---name: project-architecturedescription: Designs project system architecture. Use before project-plan for Platform, cross-system, or four-plus-epic work.---# project-architectureInput: `$ARGUMENTS` (focus areas, constraints).Output: `[PROJECT_DIR]/architecture.md`.Template: `.speck/templates/project/architecture-template.md`.Prereq: `project.md`, `context.md` (REQUIRED). Runs before `/project-plan`.## 0. TemplateRead `.speck/templates/project/architecture-template.md` before writing.## 1. Play levelRead `.speck/project.json` → `play_level`.| Level | Action ||-------|--------|| Sprint | STOP — skip formal architecture; `/project-promote` when ready || Build | Optional — proceed only if user confirms or tech uncertain || Platform | Full flow |## 2. Load context- `project.md`, `context.md` (STOP if missing → `/project-context`)- `constitution.md`, `ux-strategy.md`, `*-research-report-*.md`- Brownfield: `project-landscape-overview.md`, `project-import.md`- Recipe: `_active_recipe:` → `.speck/recipes/[name]/recipe.yaml` (`stack`, `architecture`, `patterns`, `external_services`)**Mode**: landscape exists → brownfield (as-is + to-be); else greenfield.## 3. JIT researchFollow `.cursor/skills/just-in-time-research/SKILL.md`. Gap areas: stack evaluation, patterns, performance, integration, migration (brownfield).Deep research needed → PAUSE: `project-architecture-research-prompt-[topic].md` → user saves `project-architecture-research-report-[topic].md` → re-run.## 4. BrownfieldExtract from landscape: pattern, components, stack, data models, APIs, deployment, debt. Document current state; propose evolution aligned with `context.md` constraints.## 5. GreenfieldDecide: pattern, deployment targets, quality attributes, frontend/backend/DB/integration choices. Verify against `context.md` (team skills, infra limits).Recipe active → pre-fill from recipe; ask only gaps.## 6. Write architecture.mdFill template. Include: components, stack rationale, data/security/performance/scaling/integration/deployment/ops. ASCII or Mermaid diagrams. Cross-reference epic boundaries and shared components.Embed research in "Research Informing This Architecture."## 7. Validation checklistSupports functional + non-functional reqs; fits constraints; clear epic boundaries; independent epic development; security + scale addressed.## 8. Next| Step | Notes ||------|-------|| `/project-design-system` | UI-heavy projects || `/project-plan` | Consumes architecture.md || `/project-validate` | Post-implementation only |## NEVER / ALWAYS- NEVER plan Platform without architecture feeding `/project-plan`- NEVER contradict `context.md` constraints silently- NEVER skip as-is documentation in brownfield- ALWAYS read template first- ALWAYS document trade-offs and evolution path

Frequently asked questions

Project Architecture