v1.0 - Initial Skills System¶
Released: November 2025
The initial release of DevEnv, transforming static instruction files into a modular skills-based development system.
Highlights¶
- Skills Architecture: Modular AI modules that Claude orchestrates automatically
- 5 Core Skills: Orchestrator, PRD writer, schema architect, backend bootstrapper, feature builder
- Two-Directory Structure:
.claude/for AI behavior,.devenv/for standards - Slash Commands:
/start-projectand/discovery-only
The Transformation¶
Before: Static Instructions¶
.devenv/
├── foundations/
│ ├── product-development-foundation.md ← Read manually
│ └── roadmap-generator-prompt.md ← Copy/paste to Claude
├── saas/
│ ├── saas-implementation-guide.md ← Follow week-by-week manually
│ └── saas-tech-stack.md ← Reference when needed
└── README.md ← Documentation
Usage: Copy files, read guides, follow steps manually.
After: Intelligent Skills¶
.claude/skills/
├── saas-project-orchestrator/ # Meta-skill: guides entire SDLC
├── product-brief-writer/ # Auto-creates PRDs
├── schema-architect/ # Auto-designs schemas
├── backend-bootstrapper/ # Auto-sets up Apso
└── feature-builder/ # Auto-implements features
Usage: Say "Build a SaaS for X" and Claude orchestrates everything.
The 5 Skills¶
1. saas-project-orchestrator (Meta-Skill)¶
Purpose: Guides you through the entire SaaS project lifecycle
Triggers: "Start a new SaaS project", "Build a full-stack application"
Orchestrates: - Phase 0: Discovery & planning - Phase 1: Schema design - Phase 2: Backend setup - Phase 3: Frontend setup - Phase 4: Authentication - Phase 5: Feature implementation - Phase 6: Testing & deployment
2. product-brief-writer¶
Purpose: Creates comprehensive Product Requirement Documents (PRDs)
Triggers: "Write a product brief", "Create a PRD"
Output: docs/product-requirements.md with problem statement, personas, MVP features, success metrics, timeline
3. schema-architect¶
Purpose: Designs database schemas with multi-tenancy built in
Triggers: "Design a database schema", "Create data model"
Output: .apsorc schema file, entity relationships, multi-tenant architecture, optimized indexes
4. backend-bootstrapper¶
Purpose: Sets up production-ready Apso backend with generated API
Triggers: "Set up the backend", "Create the API"
Output: Complete NestJS backend, REST API with CRUD endpoints, PostgreSQL database, OpenAPI documentation
5. feature-builder¶
Purpose: Implements complete features full-stack
Triggers: "Implement a [feature name] feature", "Add [functionality]"
Output: Backend endpoints and logic, frontend UI components, tests and documentation
Architecture: Brick by Brick¶
┌────────────────────────────────────────────────────┐
│ You: "Build a SaaS for project management" │
└───────────────────┬────────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────┐
│ Claude: Loads orchestrator skill │
└───────────────────┬────────────────────────────────┘
│
┌───────────────┼───────────────┐
▼ ▼ ▼
┌───────┐ ┌─────────┐ ┌──────────┐
│ PRD │ → │ Schema │ → │ Backend │ → ...
│Writer │ │Architect│ │Bootstrap │
└───────┘ └─────────┘ └──────────┘
│ │ │
▼ ▼ ▼
PRD.md .apsorc API+DB
Each skill is a "brick of narrow intelligence" that Claude orchestrates with general intelligence.
Two-Directory Structure¶
.claude/ - AI Behavior¶
| Directory | Purpose |
|---|---|
commands/ |
Slash commands users can invoke |
skills/ |
Specialized AI modules |
templates/ |
Prompt templates |
.devenv/ - Development Environment¶
| Directory | Purpose |
|---|---|
setup/ |
Automation scripts and templates |
docs/ |
Reference documentation |
standards/ |
Development standards and rules |
Slash Commands¶
/start-project¶
When to use: Starting a brand new SaaS product
What it does:
1. Invokes the saas-project-orchestrator skill
2. Guides through structured discovery
3. Generates schema, product brief, roadmap
4. Leads into implementation
/discovery-only¶
When to use: Major new features, idea validation, stalled projects
What it does: - Runs discovery process - Produces requirements document - Stops there - you choose next steps
Time Savings¶
| Task | Manual | With Skills | Savings |
|---|---|---|---|
| Complete project setup | 2-3 days | 30 minutes | 90% |
| Schema design | Half day | 1-2 hours | 75% |
| Backend bootstrap | 2-3 days | 10 minutes | 95% |
| Feature implementation | 1-2 weeks | 1-3 days | 70% |
| Complete MVP | 16 weeks | 12 weeks | 25% |
Quality Improvements¶
| Metric | Before | After |
|---|---|---|
| Standards enforcement | Manual | Automatic |
| Multi-tenancy | Sometimes forgotten | Always included |
| Documentation | Partial | Complete |
| Best practices | Depends on developer | Enforced by skills |
Getting Started¶
Full Project¶
Specific Tasks¶
Philosophy¶
Skills don't just generate code - they orchestrate an entire methodology:
- Product planning produces PRDs
- Architecture design produces schemas
- Implementation produces code
- Testing produces test suites
Each skill is modular, controllable, shareable, and evolutionary - add more intelligence over time.