chicommerce

CI/CD pipeline requirements and deployment standards. Use when (1) Setting up CI/CD pipelines, (2) Debugging CI failures, (3) Configuring deployment workflows, (4) Managing staging/production releases, (5) Investigating build failures. Covers CI gate requirements, merge policies, auto-deploy to staging, production approval process.

Coding standards for new/reviewed code, UI/UX, security, accessibility.

Coding style standards, security guidelines, and accessibility requirements. Use when (1) Writing new code, (2) Reviewing code for style/security, (3) Implementing UI/UX features, (4) Addressing security concerns, (5) Ensuring accessibility compliance. Covers naming conventions, formatting, security best practices (no secrets/PII), accessibility standards (semantic HTML, keyboard nav), and responsive design.

Prevent connection pool exhaustion when querying Railway PostgreSQL database. Use when (1) Running database queries from local environment, (2) Diagnosing "too many clients" errors, (3) Writing Python scripts that query production DB, (4) Checking connection pool status. CRITICAL - Always close connections immediately after use, use context managers, check pool status before queries.

Database schema management using idempotent sync script instead of Alembic migrations. Use when (1) Adding new database tables, (2) Adding new columns to existing tables, (3) Modifying database schema, (4) Deploying to production, (5) Syncing schema across environments. REQUIRED APPROACH - ALWAYS use scripts/sync-production-schema.py with --dry-run first, NEVER run Alembic migrations directly in production.

Pre-delivery acceptance checklist and reusable mini-prompts for common tasks. Use when (1) Preparing to mark story as Delivered, (2) Final PR review before merge, (3) Need quick prompt templates for classification/TDD/refactoring/PR composition, (4) Verifying completeness of implementation. Includes default loop (Plan → Implement → Artifacts → PR → Verify → Deliver) and acceptance criteria.

Complete workflow for email marketing campaigns with conversion tracking and trial activation. Use when (1) Creating email campaigns, (2) Sending campaign emails via Resend API, (3) Tracking conversions and clicks, (4) Activating trials for campaign users, (5) Generating campaign reports, (6) Sending reminder emails. CRITICAL - Follow Resend rate limits (2 emails/second), use UPPERCASE for PostgreSQL enums.

Enforces ZERO TOLERANCE file placement rules for documentation and scripts. Use when (1) Creating any .md file, (2) Creating any .sh script, (3) Organizing documentation, (4) Writing guides or reports, (5) Adding utility scripts. CRITICAL RULES - NEVER create .md files in root directories (except README.md, CLAUDE.md), NEVER create .sh scripts in backend (except start.sh), ALL documentation goes in docs/ subfolders, ALL scripts go in scripts/ folder.

Git commit, PR, and branching standards with ZERO TOLERANCE for AI attribution. Use when (1) Creating commits, (2) Writing commit messages, (3) Creating pull requests, (4) Writing PR descriptions, (5) Branching or merging code. ABSOLUTE RULE - NEVER include "Claude", "Anthropic", "AI-generated", emojis with "Generated with", or any AI tool attribution in commits, PRs, issues, or documentation.

Enforces Test-Driven Development (TDD) with BDD-style tests and mandatory test execution. Use when (1) Writing any new code or feature, (2) Fixing bugs, (3) Refactoring existing code, (4) Creating pull requests, (5) Closing issues. CRITICAL RULE - Tests MUST be actually executed with proof of passing status and coverage >= 80% before ANY commit, PR, or issue closure.

Story management, estimation, and Shortcut integration for backlog workflow. Use when (1) Starting new work from backlog, (2) Estimating story points, (3) Creating feature/bug/chore stories, (4) Defining acceptance criteria, (5) Working with Shortcut/issue tracking, (6) Classifying work types. Covers Fibonacci estimation (0/1/2/3/5/8), branch naming, story types, and TDD workflow integration.

Enforce unique featured images for Strapi blog posts. Use when (1) Creating new blog posts, (2) Updating blog post images, (3) Auditing blog content for duplicates, (4) Publishing blog content. ZERO TOLERANCE - Every blog post MUST have a unique featured image, never reuse images across posts.

Enforce mandatory slug parameter for Strapi blog post updates. Use when (1) Updating Strapi blog posts via MCP, (2) Creating blog content, (3) Fixing blog post issues. ZERO TOLERANCE - WITHOUT SLUG = WORK IS NULL AND VOID. The slug is required for blog detail pages to work correctly.

Generate comprehensive weekly progress reports for AINative platform. Use when (1) Creating end-of-week status reports, (2) Summarizing commits and features, (3) Documenting bug fixes and improvements, (4) Tracking sprint progress, (5) Preparing stakeholder updates. Analyzes git commits, GitHub issues, and PRs to produce structured markdown reports.