- Home
- Skills
- Agents & Orchestration
- Software Architect
Works with the AI Agents you already use
Software Architect
Opinionated architecture planning that picks a stack, defines data models, and sets strict "will-not-build" boundaries.
$10
Software Architect
Example session with this skill installed
Review docs/requirements.md for 'TaskFlow' (local-first productivity tool) and define the architecture. Focus on the core note-taking slice. Use docs/architecture.md for output.
- Read your context and instructions
- Compiled the software architect
Processed requirements for TaskFlow. I have defined a local-first architecture focused on the core note-taking slice, emphasizing low latency and durability.
Architecture: TaskFlow
Header
- Product: TaskFlow
- Slice Goal: Core note-taking and persistence
- UI: Yes
- Hosting: local-first
- Status: ready
Drivers
- Low Latency: Interaction must feel instantaneous on desktop (ref: NFR-1).
- Local Persistence: Data must survive process restart without network (ref: FR-4).
- Single Operator: No multi-user synchronization or identity required for this slice (ref: Out-of-Scope).
Chosen Stack
- Language: TypeScript 5.0+
- Runtime: Electron (Node.js 20+)
- UI Toolkit: React with Tailwind CSS
- Storage: SQLite (via
better-sqlite3)
Data Model
| Entity | Fields | Type | Key |
|---|---|---|---|
Note | id, content, created_at, updated_at | UUID, Text, ISO8601, ISO8601 | PK (id) |
Tag | id, label | UUID, String | PK (id) |
Contracts
StorageProvider.saveNote(note: Note): Promise<void>- Errors:
DiskFull,DatabaseLocked
- Errors:
StorageProvider.getNotes(): Promise<Note[]>UI.renderEditor(noteId: string): void
ADRs
- Decision: SQLite over JSON files.
- Rationale: Better query performance for future search features and ACID compliance for durability.
- Alternatives Rejected: LocalStorage (size limits), MongoDB (operational overhead).
Will-Not-Build
- User Accounts/Auth: The application is tied to the local machine user.
- Cloud Sync: Out of scope for this slice; no external API calls.
- Markdown Preview: Requirements specify plain-text only for P0.
Next steps
- Review the
docs/architecture.mdfile for sign-off. - Initialize the repository using the TypeScript/Electron stack.
- Hand off to the
senior-plannerskill to generate implementation tasks.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Developers often waste time debating framework menus or over-engineering infrastructure for simple requirements. Without a clear contract between design and implementation, projects suffer from scope creep and "just in case" microservices.
What it does
- Analyzes requirements and UX handoffs to select a single, concrete technology stack.
- Defines a lean data model focused exclusively on P0 features.
- Specifies module boundaries and API contracts (in-process or network) for implementation.
- Generates an explicit "will-not-build" list to prevent unauthorized scope expansion.
- Documents architectural decisions (ADRs) including rationales and rejected alternatives.
Frameworks & tools
Agnostic. Works with any stack including React, Python, SQLite, Node.js, and local-first or hosted environments.
Why this beats prompting it yourself
Generic prompts often return generic "best practices" or a list of five options. This skill forces a single opinionated path, strictly respects out-of-scope boundaries, and ensures every architectural choice is tied to a specific requirement driver.
Use cases
- Transforming a business requirements document into a technical blueprint.
- Setting boundaries for junior developers by defining what NOT to build.
- Resolving stack indecision by identifying the specific drivers that force a choice.
- Creating clean module contracts before a single line of application code is written.
Known limitations
Does not perform implementation, cloud infrastructure setup, or task sequencing. It blocks execution if hosting intent or UX requirements are missing.
Requires pre-existing requirements document. Will not select cloud providers if hosting is undecided. Does not write code or infrastructure scripts.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago