genesis-architect

Solid

Use when starting a new project - scans 15-20 real GitHub repos and mines their Issues for pitfalls before writing a single file. No other scaffolding tool does this automatically. Identifies real architecture regrets from production codebases, then builds a working scaffold with tests, CI/CD, security defaults, and an ADR explaining every decision. After scaffolding, stays active as a research companion. Triggers on: "genesis init [vision]", "I want to build X", "scaffold", "new project", "set up project", "start building", "create a tool", "make a CLI", "bootstrap", "בנה פרויקט", "צור פרויקט", "התחל פרויקט".

Code & Development 18 stars 5 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- Skill metadata (version, author, license, optional_mcps, fallback) lives in manifest.json and plugin.json. Claude Code only reads `name` and `description` from this frontmatter; extra keys are silently ignored, so they belong with the rest of the package metadata, not here. --> # Genesis Architect > Research first. Build once. The 10 minutes spent on research save 10 hours of refactoring. --- ## Language Detection Detect the user's language from their first message. Respond in that language throughout all phases. Default to English for unrecognized languages. --- ## Invocation When the user writes `genesis init [description]`, extract the vision and skip Phase 1 questions. Auto-detect archetype and scale from the description. These are surfaced for confirmation in Phase 5 before any files are created - never silently assumed. Phase 0 always runs regardless of invocation method. `genesis init --from-prd [file]` - read a PRD file (e.g., from idea-os or similar product planning tools). Extract: project name, core purpose, target users, scale, constraints. Use as Phase 1 answers and as additional search signals in Phase 2. Skip Phase 1 questions entirely. `genesis init --from-team-config` - read `.genesis.json` from the current directory. Restore language, tier, and research context from a teammate's prior Genesis run. Skip Phases 1-5. Required fields in `.genesis.json`: `language`, `tier` (minimalist|scalable), `vision`. If any required field is missing, abort wi...

Details

Author
maioio
Repository
maioio/genesis-architect
Created
2 weeks ago
Last Updated
2 days ago
Language
Python
License
MIT

Integrates with

Related Skills

Code & Development Featured

code-reviewer

Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

9,342 Updated 5 days ago
Jeffallan
Code & Development Featured

security-reviewer

Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews, dependency audits, secrets scanning, or compliance checks. Produces vulnerability reports, prioritized recommendations, and compliance checklists.

9,342 Updated 5 days ago
Jeffallan
Code & Development Featured

parallel-investigation

Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.

745 Updated 1 months ago
rohitg00