convez.ai
InicialPluginScore · de 0 a 100

Claude Code slash commands for agent-driven iOS development — spec to release in 8 stages

Instalação

$npx convez-ai akshaypimprikar/pragma

1 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

Estrelas
4
Forks
0
Acompanhando
1
Saúde
71%
Último commit
há 10 horas
Versão
v2.1.3
Issues abertas
30
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

Pragma

You approve twice. Claude ships the rest.

License: MIT Claude Code Platform Swift

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:

  1. Fill in CLAUDE.md — add your architecture rules and any project-specific constraints
  2. Seed .claude/context/invariants.md with your non-negotiable rules before running /feature

What You Get

Three layers installed into your project:

LayerSourceWhat it does
Agent commands.claude/commands/13 Claude Code slash commands covering the full SDLC
CI pipelinescaffold/.github/workflows/3 GitHub Actions workflows — PR checks, UI tests, and release
Support scriptsscripts/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

CommandWhat it does
/spec "feature idea"Proposes 2–3 approaches, you choose, spec doc saved
/plan docs/specs/my-spec.mdTurns an approved spec into a task-by-task implementation plan
/feature docs/plans/my-plan.mdExecutes an approved plan — TDD, one commit per task
/gatesVerifies build, full test suite, and architecture compliance before PR
/reviewReviews a PR for architecture compliance
/testWrites tests for a feature branch — run in parallel with /review
/bugfix "description"Regression test first, then fix — test-first always
/release 1.0.0Version bump, changelog, PR to main, git tag

Utility

CommandWhat it does
/designEstablishes visual design tokens — run before /spec on UI features
/pipeline-reviewAudits the pipeline for drift, gaps, and inefficiencies
/statusReconstructs where work stands — use to resume any session
/trim-contextTrims accumulated context after completing a plan
/sync-workflowSyncs this scaffold with your project's latest conventions

CI Layer

Three GitHub Actions workflows install into your project alongside the commands:

WorkflowTriggerWhat it enforces
pr-checks.ymlPR to develop or mainUnit + integration tests, coverage ≥ 60% (warn < 80%)
ui-tests.ymlPR to develop or main, push to eitherUI tests
release.ymlTag 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:

  1. Write the failing test — confirm it fails for the right reason
  2. Implement the minimal code to make it pass
  3. Run the full test suite — no regressions allowed
  4. 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 edit project.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:

  1. Copy .claude/commands/, .claude/context/, scaffold/.github/workflows/, and scripts/ into your project (place the workflows at .github/workflows/)
  2. Replace <AppName> with your module name in each command file
  3. Replace YOUR_PROJECT and YOUR_SCHEME in the three workflow files
  4. Update CLAUDE.md with your build commands, simulator target, and architecture rules
  5. Populate .claude/context/invariants.md with your non-negotiable rules
  6. Update the Architecture Rules checklist in /review to 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.

Ver o original no GitHub

Bom para

Relacionados