Results for “code-interfaces”

Provides idiomatic Go patterns, best practices, and conventions for writing, reviewing, and refactoring Go code.

Design comfortable, accessible dark mode interfaces with proper color adaptation, contrast, and surface hierarchy.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Guides coding workflows with planning, implementation, verification, and testing, storing user preferences locally on request.

Analyzes codebases to map entry points, execution flows, architecture layers, patterns, and dependencies before new development begins.

Generates multiple radically different interface designs for a module, compares them, and synthesizes the best approach.

Analyzes codebases to understand existing features, tracing entry points, execution paths, architecture layers, patterns, and dependencies before new development.

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md.

Establishes baseline cross-project coding conventions for naming, readability, immutability, and code-quality review, with pointers to framework-specific skills.

Design interaction flows, states, and microinteractions for usability and feedback clarity. Use when: (1) defining flows, (2) state/error handling, (3) reducing cognitive load. NOT for: final code implementation.

Finds architectural friction in a codebase and proposes deep-module refactors to improve testability and AI-navigability, informed by the domain glossary and ADRs.

code-generation-standards

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Use for UI/UX and design-system work when Codex should convert visual direction or existing UI into reusable design tokens.

Identifies common software anti-patterns in code and suggests refactoring solutions to improve code quality.

Design the small details—triggers, rules, feedback, loops, and modes—that separate good products from great ones, based on Dan Saffer's framework.

Completely delete and rewrite a file or module from scratch when structural rot makes patching impossible, with enforced preservation of interfaces and blast radius verification.

Stop Codex, GitHub Copilot, Claude Code, and Cursor from shipping generic UI. Use UIZZE’s public catalogue of 800,000+ real web and iOS screens to extract product-specific design decisions and enforce a hard finish gate for web and iOS interfaces.

Builds production-grade web or mobile interfaces with distinctive design, modern CSS, and purposeful motion, inferring intent from the codebase without asking questions.

Foundational TypeScript patterns covering types, interfaces, generics, utility types, and common idioms. Use when writing TypeScript code, understanding the type system, or needing guidance on which specialized TypeScript skill to use. This is the entry point for TypeScript development.