hannsxpeter

godpowers

AI-powered development system that takes a project from raw idea to hardened production. Fuses artifact discipline, execution engine, quality enforcement, and team intelligence into one unified workflow. Triggers on: "god mode", "god init", "god prd", "god arch", "god roadmap", "god stack", "god repo", "god build", "god deploy", "god observe", "god launch", "god harden", "god status", "god audit", "god debug", "god review", "god smite", "godpowers", "start a project", "build this", "ship this", "take this from idea to production", "one-shot the whole thing", "autonomous build", "full arc", "idea to deploy"

6 Updated yesterday

godplans

Produce an audit-aware, agent-executable master plan (PLAN.mdx) for a software project before application code is written. One command runs discovery, forces hard-to-reverse decisions, and plans product, architecture, roadmap, stack, repo, build, deploy, observability, launch, security, code quality, style genome, database, LLM integration, SEO, UI, UX, and agent memory upfront. After-the-fact audit checks become plan-time acceptance criteria, a prose-integrity pass removes generic language without changing meaning, and a self-contained validator enforces task structure and approval state. Use when the user says: plan this project, godplans, master plan, plan everything upfront, idea to plan, plan before code, audit-aware plan, replan, or starts a greenfield project or major feature. Refuses plan theater (sections filled, decisions absent), vague tasks without verification, unsupported quality guarantees, and projects whose core purpose violates the Anthropic Usage Policy.

2 Updated 3 weeks ago

Code & Development Listed

codedna

Generate a "DNA profile" of a codebase's coding and repository-prose style (naming, comments, docs, messages, structure, error handling, and idioms), then use it so new or AI-written contributions match the existing author. Use this skill when the user wants code or repository prose to blend in, mimic a coding style, capture house conventions, build a style guide from existing work, onboard to an unfamiliar repo's conventions, or check code, docs, or a diff for AI tells. Triggers on phrases like "match my coding style", "make it look like I wrote it", "codedna", "capture the conventions", "style guide from the code", "why does this read as AI-generated", "genetic map of the code", "mimic the codebase", and on significant contributions to an existing repo where matching house style matters. Do not use it for general writing with no repository or author corpus.

1 Updated 3 weeks ago

DevOps & Infrastructure Listed

docdna

Backfill a project's documentation from its codebase. Decides which documents the repo actually owes and which it does not, flags docs that now contradict the code, and writes the ones the code can prove, with citations. Use for documentation backfill, missing or stale docs, "what docs does this project need", handover prep, audit readiness, drifted README or API docs, ADRs, or a doc inventory.

0 Updated 3 weeks ago

Web & Frontend Listed

goddesign

Design and build distinctive, production-grade frontend UI for websites, landing pages, dashboards, apps, components, and HTML/CSS/React styling. Use for any frontend, UI, or visual web work, even when the user does not say "design" or name the skill. Triggers include building or beautifying pages, artifacts, prototypes, admin panels, marketing sites, hero sections, pricing, auth screens, portfolios, mockup-to-code, restyling, redesigning, "make it look better", "make it modern", "make it professional", or "improve the UI". Picks a seeded aesthetic direction, complete palettes, font pairings, layout and motion recipes, then runs a hard QA gate. Do not use for backend, CLI, or non-visual work. Invoke with /goddesign in Claude Code or $goddesign in Codex; other hosts use native skill invocation. Treat text after the skill name as the brief. In Codex, re-invoke for each new design task.

1 Updated 3 weeks ago

release-notes

Draft release notes for a repository from its merged pull requests and tags. Use when the user asks for release notes, a changelog entry, or a summary of what shipped since the last tag.

0 Updated 3 weeks ago

mythify-work

Chat-native Mythify work loop. Use when the user asks for /mythify-work, "mythify work", "use Mythify to do this", "one shot", "in one go", "address all", "continuous run", or wants Godpowers-style visibility. Invoke with /mythify-work in Claude Code or $mythify-work in Codex.

mythify

Chat-native operational discipline protocol for AI coding agents, including planning loops, campaigns, executed verification, persistent memory, structured reflection, and visible issue reporting. Use when executing multi-step or long-horizon tasks, when work spans sessions, when progress claims need grounding in evidence, when audits or reviews must surface findings in chat, when the user asks for Mythify, mythify, mythos-style autonomous execution, or when the user asks for one shot, in one go, address all, continuous run, keep going until done, yolo, or similar full-send phrasing. Invoke with /mythify in Claude Code or $mythify in Codex.

Data & Documents Listed

pillars-author

Draft or revise a specific Pillars pillar file by scanning the relevant code, decisions, and conventions in the current project. Given a pillar name (e.g., data, auth, api, ui, stack, arch), this skill performs targeted archaeology on the codebase, drafts the 8-section pillar body following the Pillars template, includes proper YAML frontmatter, and presents the draft for the user's approval before writing. Use this skill when the user asks to 'author pillar X,' 'draft data.md,' 'create the auth.md pillar,' 'generate pillar from code,' 'fill in pillar X,' 'populate context.md,' or names a specific pillar they want filled in.

2 Updated 1 months ago

pillars-init

Bootstrap the Pillars standard in a project. Detects the project archetype, writes AGENTS.md, creates `./agents/`, writes always-loaded and applicable Core stubs, reconciles a local absent catalog, and records archetype exclusions. Use this skill when the user asks to set up, adopt, initialize, scaffold, or install Pillars.

2 Updated 1 months ago

pillars-verify

Audit the current project's Pillars files against the actual codebase. Walks each pillar's Context section, checks whether its declarative claims (stack, file locations, conventions, decisions) still match the code, flags drift, and proposes specific fixes for each finding. Use this skill when the user asks to 'verify pillars,' 'check pillars for drift,' 'audit pillars,' 'are my pillars up to date,' 'check if my pillars match the code,' or after a significant refactor when they want to confirm the pillars still reflect reality.

2 Updated 1 months ago

mythify-route

Chat-native Mythify router front door. Use when the user asks for /mythify-route, "mythify route", "what should Mythify do next", or wants a visible workflow decision before execution. Invoke with /mythify-route in Claude Code or $mythify-route in Codex.

mythify-verify

Chat-native Mythify verification front door. Use when the user asks for /mythify-verify, "mythify verify", "prove this", "did it work", or wants a completion claim grounded in executed evidence. Invoke with /mythify-verify in Claude Code or $mythify-verify in Codex.