chief-architect_skill

This skill guides solo developers by architecting personal productivity apps, analyzing context, selecting options, and orchestrating tasks across domains.

Python

648

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ananddtyagi/cc-marketplace --skill chief-architect

index.cjs13.8 KB
SKILL.md33.0 KB

Overview

This skill is a Personal App Architect that orchestrates strategic decisions for single-developer productivity applications targeting roughly 10–100 users. It analyzes project context, recommends maintainable architecture choices, and delegates implementation tasks to specialized skills. The goal is fast, low-risk delivery that preserves developer velocity and user productivity.

How this skill works

It inspects the entire project surface: code, docs, configs, tests, and user-experience signals to build a current-state architecture profile. It evaluates multiple solution alternatives against personal-app constraints (simplicity, offline support, mobile-readiness) and documents decisions with rationale. It orchestrates implementation by delegating tasks to targeted skills, managing dependencies and recovery paths. All success claims require manual verification and explicit user confirmation per the Reality-First Verification Protocol.

When to use it

Planning architecture for a solo-built productivity app
Deciding between local-first vs server-backed data approaches
Preparing a browser app for mobile deployment (Capacitor)
Reducing technical debt that slows personal development velocity
Designing a simple frontend stack (Vue + TypeScript) for maintainability

Best practices

Prioritize simple, maintainable solutions a single developer can own
Document every architectural decision and attach user-impact notes
Favor local-first data persistence (IndexedDB) with clear backup strategies
Run exhaustive local tests before any technology pivot and keep checkpoints
Use feature flags and checkpoints to manage risky changes and rollbacks

Example use cases

Analyze an existing personal app and produce a prioritized refactor plan focused on UX and velocity
Choose between IndexedDB sync vs lightweight server sync and document trade-offs
Create a task graph and delegate frontend optimizations to a Vue/Pinia specialist skill
Prepare the app for mobile by evaluating Capacitor integration and touch UX changes
Set up an ideas-file watcher to auto-process feature ideas safely with backups

FAQ

Single-developer productivity apps with around 10–100 users, where simplicity and maintainability matter more than enterprise-scale features.

Do you claim features are complete automatically?

No. Every success claim requires manual testing, screenshots or logs, and explicit user confirmation per the mandatory verification protocol.