菜单
Run Konsist architecture tests and Harmonize iOS architecture tests. Use to verify code follows project conventions after structural changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Convert acceptance criteria, Jira tickets, Gherkin scenarios, PRDs, or any product requirements into a structured spec template. Use when translating PM artifacts into actionable specs for add-*, update, migrate, or remove skills.
Scaffold a complete new feature module with all 6 submodules, source files, tests, fakes, and AGENTS.md. Use when adding an entirely new feature to the app.
Execute cross-cutting migrations — library swaps, pattern changes, API version upgrades, or architecture refactors. Handles phased rollout, coexistence, and rollback planning.
Reverse-engineer a spec from existing code — reconstructs presumed acceptance criteria, data flow, API contracts, UI states, and business rules by reading source, tests, and git history. Use when inheriting undocumented features, onboarding onto unfamiliar code, or preparing for a refactor.
Modify existing feature code across all affected layers — domain models, data, presentation, tests, and fakes. Use when changing behavior, adding fields, or enhancing existing features.
Verification pipeline with three scopes — diff (default, changed modules only), full (whole project lint + unit + arch + builds), and all (every test level + every variant + full assemble). Use after any code change.
| name | run-arch-tests |
| description | Run Konsist architecture tests and Harmonize iOS architecture tests. Use to verify code follows project conventions after structural changes. |
.agents/standards/verification.mdAfter any changes that affect:
@ContributesBinding, @CircuitInject, @Inject)./gradlew :testing:architecture-check:test
22 test classes organized in 5 categories:
| Category | Tests | What They Enforce |
|---|---|---|
architecture/ | LayerDependency, CircularDependency, ForbiddenPatterns | Import direction, no circular deps, banned API usage |
circuit/ | CircuitConventions, NamingConventions | Screen/Presenter/Event naming, sealed class (not interface), placement |
core/ | CodeHygiene, DependencyInjection, PackageConventions, VisibilityConventions, DependencyGraphScope, CoreMetroConventions, AgentDocumentation | No wildcards, @ContributesBinding coverage, package naming, minimal visibility, graph placement, metro isolation, AGENTS.md coverage |
layers/ | ApiLayer, DataLayer, DomainLayer, PresentationLayer | Immutable models, serialization placement, DI wiring, UiState conventions |
testing/ | TestDoubleConventions, TestFileNaming, TestModuleCoverage, TestModuleDI, TestBoundary, UiTestConventions | Fake naming, test file placement, DI on fakes, module isolation, Robot pattern compliance |
swift test --package-path iosApp/ArchitectureCheck
40 tests enforce Swift view conventions, test module organization, navint test conventions, E2E test conventions, and iOS architectural patterns.
Konsist failures include:
Common fixes:
{Feature}{Type} pattern@ContributesBinding, @CircuitInject, or @Inject