Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Software Architect

    1

    Opinionated architecture planning that picks a stack, defines data models, and sets strict "will-not-build" boundaries.

    $10

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Software Architect

    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
    • Generated the UI component

    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

    1. Low Latency: Interaction must feel instantaneous on desktop (ref: NFR-1).
    2. Local Persistence: Data must survive process restart without network (ref: FR-4).
    3. 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

    EntityFieldsTypeKey
    Noteid, content, created_at, updated_atUUID, Text, ISO8601, ISO8601PK (id)
    Tagid, labelUUID, StringPK (id)

    Contracts

    • StorageProvider.saveNote(note: Note): Promise<void>
      • Errors: DiskFull, DatabaseLocked
    • 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

    1. User Accounts/Auth: The application is tied to the local machine user.
    2. Cloud Sync: Out of scope for this slice; no external API calls.
    3. Markdown Preview: Requirements specify plain-text only for P0.

    Next steps

    • Review the docs/architecture.md file for sign-off.
    • Initialize the repository using the TypeScript/Electron stack.
    • Hand off to the senior-planner skill to generate implementation tasks.

    software-architect-1.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Convert BA requirements into a concrete technical stack and data model.Define module boundaries and API contracts to prevent implementation sprawl.Generate ADRs to document why specific technologies were chosen or rejected.Create a "will-not-build" list to enforce strict scope management.

    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.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Passed all security checks, Safe to install

    Listed1 month ago

    What's inside

    Frequently Asked Questions