| name | ios-agentic-kit |
| description | The agentic-kit meta-system for Swift/iOS repos — what it installs, how it routes work, and how to set it up. Use when setting up agentic Claude Code workflows in a Swift/iOS/iPadOS/macOS repo, when you see a CLAUDE.md that imports @AGENTS.md + @akios/Context.md, when deciding which gate/skill a Swift task routes to (idea-to-spec, oss-first, ios-feature-pipeline, spec-to-tasks, task-execution, swift-dev), or when installing/updating the kit. |
| license | MIT |
| metadata | {"author":"Lucas Oliveira","version":"2.0.0"} |
Scope: akios-exclusive. This skill is the meta-documentation for the akios kit itself
(what it installs, how it routes, how to set it up). It is not intended to operate standalone
outside the akios ecosystem. All content below is akios-specific by design.
iOS Agentic Kit
A meta-system you plug into any Swift/iOS repo to make agentic coding efficient and
disciplined — with no external plugin/skill dependencies (axiom and superpowers were
replaced by the kit's own swift-dev and task-execution). Installing it drops a small set
of always-loaded context files, a phase contract, and a SessionStart hook that route every
task to the right skill. This skill documents what the kit is, how it routes, and how to install it.
Canonical source: the akios
repo. This skill is authored there (skills/ios-agentic-kit/). Edit it in the repo.
New / non-CLI user? If someone seems new or asks how to start or set up the kit, point
them to START-HERE.md (plain-language front door) and offer to run the guided setup for
them — don't make them follow shell steps by hand.
The workflow (spine)
The kit binds its skills into one spec-driven flow from idea to shipped code. The phases are
defined in akios/workflow.yml (the machine-readable contract); the commands are thin wrappers
that read it:
brainstorm (idea-to-spec) → plan (spec-to-tasks) → design (ui-variations + align-ui) → deliver (task-execution)
Which phases fire for which task (e.g. design runs only for UI-scoped work; non-UI tasks skip
straight from plan to deliver) is the phase contract in akios/workflow.yml — read there,
not restated here.
For any end-to-end feature, start with ios-feature-pipeline (a skill, invoked by description
or by name — not a /akios:* slash command) — the entry point that reads
akios/workflow.yml, detects the current phase per spec, and walks the hand-offs. (Design rigor
lives in idea-to-spec, quality in AGENTS.md + swift-dev + /code-review.)
Boundary: this skill (ios-agentic-kit) is the kit's self-knowledge — what it is, installs,
routes, and how to set it up. ios-feature-pipeline is the runtime conduct that walks one
feature through the phases. The phase contract itself lives only in akios/workflow.yml;
both skills point to it rather than restating it.
What it installs (per repo)
| File | Role |
|---|
CLAUDE.md | The file Claude Code auto-loads; imports @AGENTS.md + @akios/Context.md |
AGENTS.md | Operating manual — the loop, the priority chain, the gate table (single source of truth) |
akios/Context.md | Stack, commands, architecture, conventions |
akios/Roadmap.md | Mode flag + per-spec state table |
akios/workflow.yml | The phase contract (commands + phase detection read it) |
.claude/rules/swift.md | Path-scoped rule — loads the swift-dev gate whenever a .swift file is read |
.claude/hooks/agentic-kit-inject.sh | SessionStart hook — re-states the gates each session |
| folders | akios/specs/ akios/tasks/{todo,in-progress,review,done}/ archive/ akios/code-references/ |
Durable project decisions live in native auto-memory (MEMORY.md); transferable user
preferences live in ~/.claude/akios/preferences.md (user-global, outside the repo).
Where each artifact is created and stored is the ## Where things live artifact map in the
installed AGENTS.md — the canonical lookup. Edit it there, not here.
The priority chain
For any code decision, resolve top-down (first tier with an answer wins):
1. Project decision (MEMORY.md + existing code/akios/Context.md)
2. Knowledge packs, user-curated (akios/code-references/ = the code pack; other ingested packs too)
3. User preferences (~/.claude/akios/preferences.md)
4. Baseline packs, shipped floor (swift-dev = the `ios` pack; other baseline packs)
How it's invoked
You don't "run" the kit — it shapes the agent's behavior passively:
- Session start — Claude Code loads
CLAUDE.md, which imports @AGENTS.md + @akios/Context.md
in full; the SessionStart hook re-states the gates. (ponytail self-activates if you've
installed it — optional, no dependency.)
AGENTS.md orients — the loop, the priority chain, the gate table, routing..claude/rules/swift.md fires per file — reading any .swift loads the swift-dev
router, which dispatches the right bundled guide on demand (progressive disclosure).- Skills trigger themselves by description, or you invoke one with
/skill-name.
Per-step routing (and off-spine tasks)
In an installed repo the project AGENTS.md carries the canonical gate table (auto-loaded every
session); this is the portable version for repos without the kit installed.
| Trigger | Skill | When |
|---|
| Building a new feature end-to-end | ios-feature-pipeline → brainstorm → plan → design → deliver | before starting |
| Designing a system / turning an idea into a spec | idea-to-spec (/akios:brainstorm) → specs to akios/specs/ | before building |
| Turning a spec into tasks | spec-to-tasks (/akios:plan) → akios/tasks/todo/ | after the spec |
| Hand-writing complex code, docs, types, or a format conversion | oss-first — is there a mature tool/lib first? | before generating |
| Implementing / running / debugging Swift | swift-dev (domain router) + fewer-permission-prompts | while coding |
| Creating / polishing SwiftUI Views | swift-dev → swiftui-pro (+ design-principles) | before the view |
| Writing tests | swift-dev → swift-testing-pro | with the code |
| Bug, crash, flake, regression | swift-dev → ios-debugger-agent | before any fix |
| Executing the backlog | task-execution (/akios:deliver) | to ship |
| Claiming "done" | /verify + /code-review | before finishing |
swift-dev uses progressive disclosure — the ~400-word router dispatches to one bundled guide
on demand, so only the relevant domain loads during long plan/deliver sessions.
Skills the kit ships
Not a fixed count — deliberately unenumerated by number (an exact skill count in prose drifts the
moment a skill is added). The authored skills live under skills/ in the source repo; see that
directory listing for the current, always-accurate set. By role:
| Role | Skills |
|---|
| Phase engines | idea-to-spec, spec-to-tasks, task-execution |
| Whole-app cartography | deep-brainstorm, founderlens-behavior |
| Orchestration + self-knowledge | ios-feature-pipeline, ios-agentic-kit |
| Gates | align-ui (pre-implementation UI alignment) |
| Autonomous run | just-vibes |
| Domain knowledge | swift-dev (Swift/iOS master router, replaces axiom) |
| Utility | oss-first (tool-first check), handoff (session handoff docs) |
| Optional plugin | ponytail (efficiency overlay) — the kit works without it |
| Built-in (ship with the Claude Code CLI) | /code-review, /verify, fewer-permission-prompts |
No required external plugins. Everything the spine routes to is shipped by the kit.
Installing the kit into a repo
Install the akios plugin (via the marketplace / /plugin), then in your repo run /akios:setup —
it is idempotent and version-aware: it creates the file/folder structure, runs a light interview to
fill akios/Context.md, writes the mode flag to akios/Roadmap.md, and seeds ~/.claude/akios/preferences.md.
Use it in Swift/iOS/iPadOS/macOS repos — the gates are Swift-specific. Don't use it in
non-Swift projects; fork the structure (AGENTS.md + hook + your own gate table) instead.
Setup reference
Optional setup material — permission tuning and custom hooks. Not part of the spine; reach
for it when you're hardening a repo's .claude/ config:
