ReddRadar
Topic: ai-code-governance
66 skills in this topic.
-
working-with-playground-app
This skill provides guidance for building UI/UX prototypes in the Packmind playground app. It should be used when creating a new prototype, iterating on an existing prototype, or working with files in apps/playground/. Triggers on mentions of "playground", "prototype", or direct work within the apps/playground/ directory.
PackmindHub/packmind 260
-
ux-microcopy
This skill provides senior UX writing expertise for crafting user-facing microcopy. It should be used when writing or reviewing UI text such as blank states, error messages, success messages, confirmation dialogs, tooltips, form labels, validation messages, loading states, onboarding text, CTAs, or any frontend component that communicates intention to the user. Also triggers when writing CLI output messages (progress feedback, errors, success confirmations, usage hints). Triggers on user-facing string literals in frontend code, empty state components, error boundaries, toast/notification text, modal copy, placeholder text, and CLI console.log/chalk/ora output messages.
PackmindHub/packmind 260
-
update-playbook
This skill should be used when the user wants to evaluate and update the Packmind playbook (standards, commands, skills) based on the current conversation context. Triggers on requests like "update the playbook", "sync standards", "check if we need new standards", or after significant coding sessions where patterns emerged.
PackmindHub/packmind 260
-
test-factory-patterns
This skill provides guidance for writing test factories in the Packmind codebase. It should be used when creating or updating factory functions in `**/test/*Factory.ts` files to ensure realistic test data with variety.
PackmindHub/packmind 260
-
qa-review
Review a user story implementation against its Example Mapping (EM) specification.
PackmindHub/packmind 260
-
packmind-onboard
Complete automated onboarding: analyzes codebase, creates package, and generates standards & commands via CLI. Automatic package creation when none exist, user selection when packages are available.
PackmindHub/packmind 260
-
packmind-create-standard
Guide for creating coding standards via the Packmind CLI. This skill should be used when users want to create a new coding standard (or add rules to an existing standard) that captures team conventions, best practices, or coding guidelines for distribution to CoPilot.
PackmindHub/packmind 260
-
packmind-create-skill
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends CoPilot's capabilities with specialized knowledge, workflows, or tool integrations.
PackmindHub/packmind 260
-
packmind-create-package
Guide for creating Packmind packages via the CLI. This skill should be used when users want to create a new package to organize standards, commands, and skills for distribution.
PackmindHub/packmind 260
-
packmind-create-command
Guide for creating reusable commands via the Packmind CLI. This skill should be used when users want to create a new command that captures multi-step workflows, recipes, or task automation for distribution to CoPilot.
PackmindHub/packmind 260
-
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
PackmindHub/packmind 260
-
git-commit-guidelines
Enforce git commit best practices using gitmoji + Conventional Commits format. TRIGGER when creating commits. Ensures quality-gate passes, prevents issue auto-closing (no Close/Fix keywords), includes Co-Authored-By for AI commits, and requires user approval before committing.
PackmindHub/packmind 260
-
doc-audit
Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage. Produces a structured markdown report at project root. Use when docs may have drifted from the codebase, before a release, or on a regular cadence.
PackmindHub/packmind 260
-
create-skill
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends CoPilot's capabilities with specialized knowledge, workflows, or tool integrations.
PackmindHub/packmind 260
-
create-em-spec
Create or iterate on an Example Mapping specification from various inputs (GitHub issue, Miro screenshots). Produces a structured EM spec for use with the qa-review skill.
PackmindHub/packmind 260
-
architect-executor
Use when executing a pre-written implementation plan that requires orchestrated task-by-task execution with TDD enforcement, selective code review, and smart user escalation. Use after writing-plans has produced a plan file.
PackmindHub/packmind 260
-
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
PackmindHub/packmind 260
-
adding-ai-agent-rendering-system
Implement a new Packmind AI agent rendering/deployer pipeline (single-file or multi-file) with type and registry wiring, frontend UI/docs updates, and thorough unit/integration tests to reliably support additional coding assistants and distribution formats when introducing a new agent integration or render mode.
PackmindHub/packmind 260