Bang-isme
- 31 skills
- 0 followers
- 1 week ago last updated
- ▌ Codex Creative Direction · bang-ismeUse for vague new or redesign UI prompts; decode the brief, pick visual authority, and produce three distinct directions before implementation.
- ▌ Codex Subagent Execution · bang-isme bundleUse when an approved plan has independent tasks ready for delegated execution with fresh subagents and two-stage review.
- ▌ Codex Workflow Autopilot · bang-isme bundleUse after intent is known to route build, fix, review, debug, docs, or Scrum requests into ordered workflow steps with exit criteria.
- ▌ Codex Master Instructions · bang-isme bundleUse as the top-priority baseline for Codex request classification, coding quality, dependency awareness, and completion checks.
- ▌ Codex Security Specialist · bang-isme bundleUse for security review, audit, hardening, compliance, DevSecOps, network, infrastructure, or application security with focused references.
- ▌ Codex Visual Quality Gate · bang-isme bundleUse after UI implementation to run mechanical source checks and independent rendered review with bounded inspect/fix loops.
- ▌ Codex Systematic Debugging · bang-isme bundleUse for bugs, test failures, broken behavior, or unexpected results; enforces 4-phase root-cause debugging before fixes.
- ▌ Codex Execution Quality Gate · bang-isme bundleUse before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
- ▌ Codex Logical Decision Layer · bang-isme bundleUse when work is ambiguous or has multiple viable paths; compares options, assumptions, evidence, tradeoffs, and the best next action.
- ▌ Codex Intent Context Analyzer · bang-isme bundleUse before build, fix, debug, review, or docs implementation; converts prompts into structured intent JSON with goal, constraints, and routing.
- ▌ Codex Spec Driven Development · bang-isme bundleUse for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
- ▌ Codex Test Driven Development · bang-isme bundleUse before feature, bugfix, or refactor implementation when behavior can be tested; enforces Red-Green-Refactor discipline.
- ▌ Codex Verification Discipline · bang-ismeUse when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always
- ▌ Codex Branch Finisher · bang-ismeUse when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
- ▌ Codex Document Writer · bang-isme bundleUse for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
- ▌ Codex Reasoning Rigor · bang-isme bundleUse when work needs deeper thinking, less generic output, repo evidence, tradeoffs, monitoring signals, or stronger quality discipline.
- ▌ Codex Scrum Subagents · bang-isme bundleUse when work needs Scrum roles, ceremonies, backlog refinement, sprint planning, story delivery, release readiness, or role handoffs.
- ▌ Codex Docs Change Sync · bang-isme bundleUse when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
- ▌ Codex Domain Specialist · bang-isme bundleUse for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.
- ▌ Codex Design Md · bang-isme bundleUse for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
- ▌ Codex Role Docs · bang-isme bundleUse for role-scoped FE/BE/DevOps/Admin/QA project docs under .codex/project-docs to preserve micro-context across long projects.
- ▌ Codex Plan Writer · bang-isme bundleUse for complex coding requests that need a structured implementation plan with dependencies, checkpoints, and verification criteria.
- ▌ Codex Doc Renderer · bang-isme bundleUse when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
- ▌ Codex Runtime Hook · bang-isme bundleUse at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.
- ▌ Codex UI UX Design · bang-ismeUse for flows, IA, cognitive load, empty/error/loading states, content ranges, and responsive accessibility before visual decoration.
- ▌ Codex Design System · bang-isme bundleUse for UI, frontend, styling, landing page, or component work; applies grammar (surface mode, change mode, composition, motion) instead of mandatory palettes.
- ▌ Codex Git Autopilot · bang-isme bundleUse when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.
- ▌ Codex Git Worktrees · bang-ismeUse when implementation needs isolation from the current workspace; creates git worktrees with safe directory selection and baseline verification.
- ▌ Codex Project Pulse · bang-isme bundleUse when asking project status, next priority, sprint health, blockers, deadlines, risk register, or daily brief generation.
- ▌ Codex Context Engine · bang-ismeUse when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.
- ▌ Codex Project Memory · bang-isme bundleUse for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.