pragma
akshaypimprikar/pragma
Claude Code slash commands for agent-driven iOS development — spec to release in 8 stages
Instalação
npx convez-ai akshaypimprikar/pragma1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
Pragma
You approve twice. Claude ships the rest.
The complete iOS development scaffold for the agentic era — agent commands, CI enforcement, and setup automation wired together so one engineer ships at team scale.
Proven on FinanceTracker — a production SwiftUI + SwiftData app built entirely on this pipeline from day one, with specs, plans, and PRs going back to the first commit.
Quick Start · What You Get · Pipeline · Commands · CI Layer · Memory Layer · Customising · Contributing
Quick Start
git clone https://github.com/akshaypimprikar/pragma
cd pragma
./scripts/setup.sh MyApp /path/to/your-ios-project
The script copies all commands, context files, CI workflows, and support scripts into your project, substitutes your app name throughout, and generates a starter CLAUDE.md. No manual find-and-replace.
Then kick off your first feature:
/spec "describe your feature idea"
After setup:
- Fill in
CLAUDE.md— add your architecture rules and any project-specific constraints - Seed
.claude/context/invariants.mdwith your non-negotiable rules before running/feature
What You Get
Three layers installed into your project:
| Layer | Source | What it does |
|---|---|---|
| Agent commands | .claude/commands/ | 13 Claude Code slash commands covering the full SDLC |
| CI pipeline | scaffold/.github/workflows/ | 3 GitHub Actions workflows — PR checks, UI tests, and release |
| Support scripts | scripts/ | Simulator selection and coverage enforcement for CI |
Each layer is independent — adopt all three or just the commands.
Pipeline
flowchart TD
A([💡 Idea]):::dim --> B
B["/spec\n✓ you approve"]:::human --> C
C["/plan\n✓ you approve"]:::human --> D
D["/feature"]:::auto --> E
E["/gates"]:::auto --> F
F([PR opened]):::dim --> G & H & CI1
CI1["CI · pr-checks\nui-tests"]:::ci --> I
G["/review"]:::auto --> I
H["/test"]:::auto --> I
I([merge to develop]):::dim -.->|next feature| B
I --> J["/release"]:::auto --> K([tag v*.*.*]):::dim --> CI2
CI2["CI · release\nRelease build + GitHub Release"]:::ci
BUG([Bug report]):::dim --> BF["/bugfix"]:::auto --> BG["/gates"]:::auto --> BP([PR]):::dim --> BR["/review"]:::auto --> BM([merge]):::dim
classDef human fill:#3d2800,stroke:#fbbf24,color:#fbbf24
classDef auto fill:#0a1f14,stroke:#34d399,color:#34d399
classDef dim fill:#161b22,stroke:#30363d,color:#8b949e
classDef ci fill:#0d1117,stroke:#58a6ff,color:#58a6ff
You approve twice — after /spec and after /plan. Every other step is either an agent or automated CI.
Commands
Core pipeline
| Command | What it does |
|---|---|
/spec "feature idea" | Proposes 2–3 approaches, you choose, spec doc saved |
/plan docs/specs/my-spec.md | Turns an approved spec into a task-by-task implementation plan |
/feature docs/plans/my-plan.md | Executes an approved plan — TDD, one commit per task |
/gates | Verifies build, full test suite, and architecture compliance before PR |
/review | Reviews a PR for architecture compliance |
/test | Writes tests for a feature branch — run in parallel with /review |
/bugfix "description" | Regression test first, then fix — test-first always |
/release 1.0.0 | Version bump, changelog, PR to main, git tag |
Utility
| Command | What it does |
|---|---|
/design | Establishes visual design tokens — run before /spec on UI features |
/pipeline-review | Audits the pipeline for drift, gaps, and inefficiencies |
/status | Reconstructs where work stands — use to resume any session |
/trim-context | Trims accumulated context after completing a plan |
/sync-workflow | Syncs this scaffold with your project's latest conventions |
CI Layer
Three GitHub Actions workflows install into your project alongside the commands:
| Workflow | Trigger | What it enforces |
|---|---|---|
pr-checks.yml | PR to develop or main | Unit + integration tests, coverage ≥ 60% (warn < 80%) |
ui-tests.yml | PR to develop or main, push to either | UI tests |
release.yml | Tag push matching v*.*.* | Full test suite in Release configuration, GitHub Release creation |
The agent layer (/gates, /review, /test) runs locally for fast feedback before a PR is opened. CI then re-runs the same checks independently as enforcement that can't be bypassed.
Phase 2 — TestFlight upload is documented but commented out in release.yml. It requires an Apple Developer Program membership, distribution certificate, and App Store Connect API key. When you're ready, the commented block shows exactly what to add.
Memory Layer
The pipeline accumulates institutional knowledge across sessions in .claude/context/:
.claude/context/
├── invariants.md — rules no agent may override (architecture, money types, etc.)
├── decisions.md — log of every spec decision: approach chosen + reason
├── feature-log.md — record of every feature shipped
└── rejections.md — approaches ruled out, with reasons
Every agent reads these files before acting. Over time the pipeline carries the same context a senior engineer would — constraints, past decisions, and dead ends — surviving every session boundary.
Populate invariants.md before running /feature for the first time.
How the Feature Agent Works
Each task in the plan follows strict TDD:
- Write the failing test — confirm it fails for the right reason
- Implement the minimal code to make it pass
- Run the full test suite — no regressions allowed
- Commit — one commit per task, no batching
The agent never proceeds to the next task if tests are red.
Customising for Your Project
Architecture assumptions (defaults — override in CLAUDE.md):
- MVVM + Repository — views contain no business logic, ViewModels depend on protocols never concrete implementations
- SwiftData for persistence — Domain Services have zero SwiftData imports
- Swift Testing —
import Testing,@Suite,@Test,#expect()for unit/integration tests; XCUITest for UI tests PBXFileSystemSynchronizedRootGroup(Xcode 16+) — files auto-compile when placed in the correct directory; never editproject.pbxproj
Via script (recommended):
./scripts/setup.sh MyApp /path/to/your-project
Copies everything and substitutes all placeholders. Then fill in CLAUDE.md and seed invariants.md.
Or manually:
- Copy
.claude/commands/,.claude/context/,scaffold/.github/workflows/, andscripts/into your project (place the workflows at.github/workflows/) - Replace
<AppName>with your module name in each command file - Replace
YOUR_PROJECTandYOUR_SCHEMEin the three workflow files - Update
CLAUDE.mdwith your build commands, simulator target, and architecture rules - Populate
.claude/context/invariants.mdwith your non-negotiable rules - Update the Architecture Rules checklist in
/reviewto match your stack
Branch Strategy (Gitflow)
main — production, tagged on release only
develop — integration branch, all features merge here
feature/* — off develop
fix/* — off develop (hotfix/* off main)
release/* — off develop, PR to main, back-merged to develop
spec/* — off develop, for spec + plan docs
Author
Built by Akshay Pimprikar — iOS lead engineer building agentic AI pipelines.