Pdbjork Guardian Compound Engineering
Use this skill whenever building, debugging, reviewing, or improving software, business automation, AI agents, Hermes/Pi skills, or production workflows.
Loop: Plan → Work → Simplify → Review → Compound → Repeat.
Guardian checks: consent, legality, privacy, non-harm, and human flourishing.
Compound after meaningful work by updating at least one durable artifact: AGENTS.md, CLAUDE.md, docs/plans, docs/solutions, docs/brainstorms, todos, tests, scripts, runbooks, or skills.
For public prose, customer copy, docs, outreach, and social posts, use the stop-slop skill before delivery to remove AI tells, throat-clearing, vague declaratives, business jargon, and formulaic structures.
For brand, content, market, investor, social, API, security, testing, and verification work, use selected ecc-* skills where relevant, under guardian-ecc-skill-policy.
For codebase onboarding, architecture maps, domain-flow mapping, knowledge-base graphing, and change-impact analysis, use guardian-understand-anything and the installed understand* skills.
Business constraints:
- Chromebloom: never mention dropshipping/internal fulfillment in customer-facing copy.
- ULoad: legal storage-unit rental + one on-site helper only.
- X/social workflows: drafts allowed; sending/posting requires human approval unless explicitly configured.
- Secrets: never paste or store live credentials in chat/docs.