Apply to ALL ideas before presenting. If an idea fails any question, rework it before showing anyone.

Secure cryptographic patterns and deterministic weak-algorithm detection. The prose guidance covers intent and context; the script provides consistent, reference-backed PASS/WARN/FAIL verdicts.

Best practices for Git version control, branching strategies, and commit conventions. Run the convention checker on commit message batches before merge; use this prose guidance for strategy and workflow decisions (those are judgment calls the script does not make).

Modern JavaScript/TypeScript patterns, anti-patterns, and quality rules.

Use when you need the Codex Copilot equivalent of Claude Copilot /knowledge-copilot: create, link, inspect, or onboard to a shared knowledge repository.

Use when you want to invoke codex-copilot specialist agents natively in Codex, either by selecting the right specialist skill for the main session or by mapping specialists onto real Codex spawned-agent roles for delegated work.

**Voice** = constant personality (who we are). **Tone** = situational modulation (how we adapt to context).

Motion as a design language. Not decoration — communication. These patterns define how elements enter, behave, and exit as a coherent system.

Elite interaction patterns covering scroll choreography with GSAP ScrollTrigger, spring physics for drag/toggle/swipe, the elite micro-timing scale, text reveal effects, magnetic and tilt elements, and page transitions with shared element morphing. Use proactively when implementing scroll-driven choreography, applying spring physics to user-initiated interactions, selecting precise timing durations, building text reveal or magnetic effects, or engineering page transitions with shared element morphing.

Use when a request needs specialist routing before implementation, including bugs, feature work, architecture changes, UX work, security-sensitive changes, or tc-backed delivery planning.

Pythonic patterns, anti-patterns, and quality rules for clean Python code.

Security Engineer for authentication, authorization, secrets, trust boundaries, unsafe inputs, data exposure, and practical security review.

Use when you need the Codex Copilot equivalent of Claude Copilot /setup-copilot or /setup: install or verify shared Copilot tooling for Codex-native projects.

Use when you need the Codex Copilot equivalent of Claude Copilot /setup-project: wire a target repository to the shared Codex Copilot framework.

Depth, light, and material systems that elevate interfaces from flat to three-dimensional. These techniques separate premium products from generic ones.

STRIDE threat enumeration (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) via prose judgment, plus deterministic DREAD severity scoring via executable script. Covers auth, authorization, session management, PII handling, API design, cryptography, secrets management, and key storage. Use proactively when reviewing authentication, authorization, or session management, designing APIs that handle user data or PII, reviewing cryptography or secrets management, performing threat modeling on new architecture, or running security-critical code review. Run the DREAD scorer for deterministic severity bands. Fallback: @include .claude/skills/security/stride-dread/SKILL.md

Architecture patterns (monolith, microservices, CQRS, event-driven, api-gateway, scalability), ADR methodology, trade-off analysis, fitness functions, and deterministic ADR completeness scoring via executable script. Use proactively when making or reviewing significant architectural decisions, writing or auditing Architecture Decision Records (ADRs), selecting an architectural pattern, validating architecture with fitness functions, or analysing trade-offs before committing to a direction. Run the scorer for deterministic completeness checking.

Validate and fix YAML frontmatter in markdown documentation

Curated font pairings by character with type scale ratios (minor third, major third, perfect fourth), fluid typography formulas using clamp(), weight and line-height rules per context, and anti-patterns for overused or generic font combinations. Use proactively when selecting a font pairing for a brand or product, choosing a type scale ratio, implementing fluid typography for responsive scaling, avoiding generic font combinations, or setting weight, line-height, and letter-spacing rules per context.

Patterns for designing task flows, service blueprints, wireframes, and user interactions with comprehensive state coverage.