All authors
Claude Skills by lbdremy
github.com/lbdremy15 skills0 installs0 views
- BoundariesRespect the PHAX four-layer architecture (cli → app → domain ← ports ← infra) when adding or moving code.Votes: 0GitHub stars: 2
- Cli View LayerKeep CLI command files thin — parse args, call one app/ use case, render via OutputPort — no business logic in src/cli/commands/.Votes: 0GitHub stars: 2
- Effect ServicesRoute all side-effecting operations (filesystem, shell, git, clock) through port interfaces in src/ports/ using Effect dependency injection.Votes: 0GitHub stars: 2
- Infrastructure AdaptersImplement infrastructure adapters in src/infra/ behind port interfaces in src/ports/ — the only place side effects are allowed.Votes: 0GitHub stars: 2
- Model RoutingExtend the routing layer, add provider adapters, change the resolution algorithm, or add new model families in src/domain/routing/.Votes: 0GitHub stars: 2
- ObservabilityWire OpenTelemetry through the SystemTelemetry port — domain produces semantic spans, infra transports them — never bypass the port in app/ or cli/.Votes: 0GitHub stars: 2
- Phax CliOperate the phax CLI — its concepts, run lifecycle, and the canonical init → plan → run → review → publish flow. Use when driving phax, explaining it to a developer, or scripting against it. Defers to `phax --usage` for the exact command/flag contract.Votes: 0GitHub stars: 2
- Phax Decide PlanDefault arbitration doctrine for `phax artifact decide` on a plan and for the planning agent's technical arbitrations when no human is in the session — split by shippable surface, oracle first when the surface is shown, footprint discipline, model and effort left to the planner, docs last.Votes: 0GitHub stars: 2
- Phax Decide ReviewDefault doctrine for turning a headless code review's findings into a plan (`phax review-plan`) — the severity scale and its threshold, what a fix may touch, when not to plan at all, and how findings become phases.Votes: 0GitHub stars: 2
- Phax Decide SpecDefault arbitration doctrine for `phax artifact decide` on a spec — how to answer a spec's §9 open questions when no human is in the session; adopt the recommendation unless a named principle says otherwise, argue for the abandoned option first, escalate what you may not decide, and emit decisions as data.Votes: 0GitHub stars: 2
- Phax PlanningWrite or review a plan.md that `phax run` extracts and `phax plans lint` checks — phase structure, required fields, model/effort, commit metadata.Votes: 0GitHub stars: 2
- Phax SpecWrite or review a spec under docs/specs/ that the phax-planning skill will turn into a plan.md — functional behavior and consumption surface, EARS requirements, testable acceptance criteria, lifecycle and traceability.Votes: 0GitHub stars: 2
- State MachinesTransition RunState and PhaseState only through the explicit functions in src/domain/state.ts — never mutate state-bearing fields directly.Votes: 0GitHub stars: 2
- Validation BoundariesDecode every external input (files, env vars, CLI args, API responses) through an Effect Schema before it crosses into the domain.Votes: 0GitHub stars: 2
- ArchiveFunctional specification.Votes: 0GitHub stars: 2