Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion .claude/skills/tina4-architect/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,17 @@
---
name: tina4-architect
description: >
Use whenever a user is starting a NEW Tina4 project OR the working directory has no TINA4.md / no plan/ folder yet. Trigger phrases: "I want to build X", "start a new tina4 project", "plan this", "architect this", "which framework should I use", "how should I structure this", "which database", "how do I deploy". Owns the decisions BEFORE any file is scaffolded: backend language, database, session backend, cache, queue, auth, realtime, AI provider, deployment target, project layout. Then maps the user journeys, the system flows, and the completeness net (the states, edges, authz, failure, and concurrency that complex builds miss) so features are derived from real user goals, not invented. Also triggers on "map the user journey", "what's the flow", "what are we missing", "trace the system". Records the choices in TINA4.md and seeds plan/ with goals, journeys, flows, and initial ADRs. Hands off to the matching tina4-developer-<lang> skill for implementation. Never runs on an already-scaffolded project with a TINA4.md unless the user explicitly asks to re-architect.
Use whenever a user is starting a NEW Tina4 project OR the working directory has no TINA4.md / no
plan/ folder yet. Trigger phrases: "I want to build X", "start a new tina4 project", "plan this",
"architect this", "which framework should I use", "how should I structure this", "how do I deploy".
Owns the decisions BEFORE any file is scaffolded: backend language, database, sessions, cache,
queue, auth, realtime, AI provider, deployment, project layout. Then maps the user journeys, the
system flows, and the completeness net (the states, edges, authz, failure and concurrency that
complex builds miss) so features come from real user goals, not invention. Also triggers on "map the
user journey", "what's the flow", "what are we missing", "trace the system". Records the choices in
TINA4.md and seeds plan/ with goals, journeys, flows and initial ADRs. Hands off to the matching
tina4-developer-<lang> skill. Never runs on a scaffolded project (TINA4.md present) unless the user
asks to re-architect.
---

# Tina4 Architect — decisions before code
Expand Down
Loading