Claude Skills by tonone-ai

Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".

Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".

Run human-to-agent migration - audit which roles can be agent-assisted or replaced, design the transition playbook, and manage the offboarding of displaced roles. Use when asked to "which roles can agents replace", "how do we transition to AI-first ops", or "build our agent migration plan".

Build onboarding playbook - day 1 through week 4 checklist, access provisioning, context transfer, and success milestones. Use when asked to "build an onboarding process", "how do we onboard new hires", or "reduce time to productivity for new joiners".

Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".

Design performance management system - review cycles, calibration process, career ladder, and PIP framework. Use when asked to "build a performance review process", "design career levels", "how do we handle underperformers", or "run a review cycle".

People reconnaissance - audit org design, hiring pipeline, comp structure, onboarding, and performance systems to understand what is working and where the constraint is. Use when asked to "audit our people ops", "what is broken in our hiring", "review our org structure", or "before designing a comp framework".

Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".

Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".

Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".

Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".

Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".

Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".

Motion design — produce HTML animations and export MP4/GIF with optional BGM. Use when asked to "animate this", "create a motion design", "make an intro animation", "product launch animation", "promo video", "export MP4", "export GIF", "60fps animation", "animated logo", or "motion graphics". Delivers a self-contained HTML animation plus rendered video exports. Not for micro-interactions in production code — use /prism-ui for that.

Use when asked to audit UI for visual quality, check design consistency, review brand alignment, evaluate design system compliance, or find visual issues before a launch. Examples: "audit our UI", "check visual consistency", "review the design for issues", "is our UI on-brand", "find visual bugs", "design QA before launch".

Use when asked to create a brand identity, define visual design direction, generate a color palette or type system, build a style guide, or establish the look and feel for a product. Examples: "create a brand for X", "define the visual identity", "what colors should we use", "build a style guide", "design system foundations".

Translate a design brief — structured I-Lang or plain English — into a concrete DESIGN.md and optional HTML token preview. Resolves 8 dimensions (palette, accent, typography, display font, layout, mood, density, constraints) to specific CSS tokens. Use when asked to "create a design brief", "write a DESIGN.md", "define the design system", "design brief for X", "what tokens should we use", or "I-Lang brief".

Use when asked to design a UI component, specify a button, input, card, modal, badge, or any interactive element. Examples: "design a button component", "spec out the input field", "define the card component states", "create a component spec for Prism", "what should the dropdown look like".

Expert 5-dimension design critique — philosophical, scored, actionable. Use when asked to "critique this design", "expert review", "score my design", "how does this look", "is this good design", "design feedback", or "review this UI". Different from /form-audit (which is technical QA for consistency/compliance) — form-critique evaluates design as a craft object: philosophy, hierarchy, execution, function, and innovation each scored 0–10 with a punch list. Add "as a report" or "give me a visua...

Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".

Design direction advisor — generates 3 differentiated visual directions with live HTML demos for selection. Use when the brief is vague ("make something nice", "pick a style", "explore directions"), when no design system exists, or when the user wants to compare visual approaches before committing. Richer than /form-style: produces actual visual demos, not just recommendations. Trigger words: "design direction", "style exploration", "pick a direction", "what should this look like", "give me o...

Use when asked to design an email template, newsletter, drip campaign email, transactional email, or any HTML email asset. Examples: "design a welcome email", "create a newsletter template", "make an onboarding email sequence", "design a password reset email", "build an email campaign".

Theory-backed design audit — names the principle violated, cites the source, shows the fix. Use when asked to "evaluate design quality", "check if this follows design principles", "theory check", "design exam", "audit against best practices", or "what's wrong with this design".

Use when asked to create a logo, design a brand mark, generate a logo concept, or produce any logo asset. Examples: "create a logo for X", "design a brand mark", "make me a logo", "generate logo concepts", "logo for our product".

Use when asked to design iOS or Android mobile app screens, create mobile UI, spec mobile flows, or produce screen designs for a native app. Examples: "design the onboarding screens", "spec the checkout flow for iOS", "design a home screen for Android", "create mobile UI for this feature".

Use when asked to generate a color palette, create industry-matched colors, or pick colors for a product type. Examples: "color palette for fintech", "healthcare app colors", "SaaS brand colors"

Use when asked to design social media graphics, ad creatives, or marketing assets. Examples: "design a LinkedIn post for our launch", "create ad creatives for our campaign", "make an Instagram story", "design a Twitter card", "create a banner ad", "social assets for the product announcement".

Use when asked to select a UI style, choose a design direction, pick a visual approach for a product, or match a style to an industry. Examples: "what style fits a fintech app", "choose between neumorphism and glassmorphism", "design direction for healthcare SaaS"

Use when asked to define a design token system, create tokens, document tokens, set up CSS custom properties, build a Tailwind token config, establish a spacing scale, define color semantics, or bridge design decisions to code. Examples: "set up design tokens", "define our token system", "create CSS variables for the design system", "document our color tokens", "establish a spacing scale".

Use when asked to design a landing page, marketing website, or any web presence intended to convert or inform. Examples: "design a landing page for X", "create a marketing site", "we need a homepage", "design our website", "build a page for our launch".

Draft board resolutions, consent documents, and meeting minutes.

Draft equity plan documents — option grants, vesting schedules, 409A notes.

Survey corporate documents — articles, bylaws, cap table, board resolutions.

Integrate API quality gates into CI — linting, breaking change detection, and coverage checks.

Design an API linting ruleset — style rules, severity levels, and custom organization conventions.

Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt.

Select and pair fonts for a product — brand display, UI body, and monospace.

Audit existing typography in a codebase — find inconsistencies, hardcoded sizes, and hierarchy gaps.

Design a type scale and hierarchy — sizes, weights, line-heights, and named tokens.

Design a layout system — spacing scale, grid columns, and layout primitives.

Audit existing layout patterns in a codebase — find ad-hoc spacing, inconsistent grids, and missing primitives.

Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority.

Audit guardrail coverage — bypass vectors, false positive rates, policy gap analysis, red-team scenarios.

Design guardrail layers — input classifiers, output validators, PII scrubbers, policy rule engines.

Map current AI safety controls — filter inventory, coverage gaps, latency impact, incident history.

Audit existing API documentation for completeness, accuracy, and developer experience.

Survey documentation coverage across an API or SDK — find undocumented endpoints and gaps.

Write API reference documentation for an endpoint or SDK method.

Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".

Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".