pedro-angel
UserA portable, agent-agnostic engineering methodology for AI coding agents — AGENTS.md + skills + per-agent adapters, with deterministic git controls.
Categories
Indexed Skills (22)
acceptance-tests-observable-outcomes
Use when you need to prove a feature actually delivers its intended outcome to a user or caller, not just that its code paths run — write executable acceptance tests against real, observable outcomes, derived from the spec before or independent of the implementation.
additive-default-off-feature-flags
Use when adding any new capability to a working system — ship it behind a flag or optional collaborator that defaults to prior behavior.
adversarial-lens-review
Use when a spec, plan, or implementation must be independently reviewed before it is trusted, committed, or advanced to the next phase — dispatch a fresh reviewer per named lens whose job is to refute the artifact, not confirm it.
autonomous-self-improvement-loop-safety
Use when building automation that edits, tests, or deploys itself — an agent that regenerates its own code, a self-updating pipeline, any loop that modifies the thing running it.
battle-testing-on-real-infra
Use when about to call any integration, deployment, or hard guarantee "done" — prove it live end-to-end and capture the run as evidence.
configuration-single-source-of-truth
Use when a value (project id, model, threshold, rubric) would be duplicated across Makefile, scripts, docs, and code — collapse to one source.
currency-and-audit-before-trust
Use when making a load-bearing or security-relevant claim, or reusing inherited or unfamiliar code — treat recalled facts and unread code as unverified until re-grounded against the live source, and disposition every dangerous surface rather than eyeballing it.
decision-memory
Use when a decision, gotcha, or preference would otherwise be re-derived next session — capture it as an indexed note, then verify before trusting stale ones.
definition-of-done-tooling
Use when about to claim work is complete, shippable, or ready to release or tag a milestone — run a script that reads declared criteria and emits GO/NO-GO instead of asserting completion from memory; the author never self-certifies.
dev-environment-facade
Use when wiring a project's dev workflow (local stack, test tiers, gates, docs), or when naming make targets in a repo that has siblings — build a thin self-documenting Makefile facade over real scripts, name targets from the shared cross-repo vocabulary, and split env files by owner so targets consume them but never write them.
docs-as-deliverable
Use when shipping or handing off code — treat docs as a first-class deliverable — present-tense, diagrammed-as-code, verified against reality, reader-tested.
environment-research
Use when a spec or plan is about to depend on a dependency, library, API, CLI, or platform whose real behavior you have not personally observed — run a small real experiment before trusting docs or memory, and let the observed result outrank documentation when they disagree.
evidence-over-deference
Use when the human's request rests on a premise you can check, contradicts evidence or a recorded principle, or proposes a direction you have not independently weighed — weigh the strongest alternative before taking a stance, challenge once with evidence before complying; their decision still wins.
grounded-verifiable-gates
Use when an LLM or agent emits decisions or claims and you need to turn fuzzy output into a verifiable, regression-protected signal.
hexagonal-with-enforced-contracts
Use when building an app that touches external systems (LLMs, DBs, cloud SDKs, HTTP APIs) — isolate a framework-free core behind ports a linter enforces.
honest-reframing-over-overclaiming
Use when a live result contradicts the hoped-for story or a metric could be gamed — state what really works and never fake a green.
parallel-agent-fan-out
Use when fanning out many write-capable sub-agents across one build — pre-wire the shared seams, own files disjointly, namespace shared state, and re-run every agent's gate yourself.
reversible-by-default-confirm-consequential
Use when an agent or automation can touch external systems — stay read-only/reversible by default and gate consequential acts behind durable human approval.
secrets-and-teardown-discipline
Use when handling credentials, IaC, or ephemeral cloud — make secrets un-committable, grant least privilege, tear down to zero, own only your scope.
spec-driven-development
Use when starting any non-trivial feature or project, or when docs and code have drifted — write the design chain before or alongside code and reconcile specs onto reality.
structural-security-boundary
Use when containing untrusted or agent-generated execution, sandboxing a worker with write/exec tools, or judging whether a guard is actually a security boundary.
surgical-changes-with-checkpoints
Use when editing code, configs, or docs — make the smallest correct diff, checkpoint before risky work, and write commits that justify themselves.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.