Results for “principles”

Understand customer decisions and turn psychological principles into practical marketing ideas. The skill explains relevant thinking tools and behavioral patterns, then suggests ethical applications for pricing, trust, messaging, onboarding, retention, and deciding which marketing problems to address first.

• Exploring why customers hesitate to purchase
• Reviewing how prices and plans are presented
• Building trust through testimonials and evidence

Design REST or GraphQL APIs by defining who will use them, what data they expose, and how requests behave. Establish error formats, versioning, pagination, and authentication, then review examples for consistency before implementation.

• Designing a new REST or GraphQL API
• Reviewing API specifications before implementation
• Establishing shared API design standards

Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.

• Designing a new REST or GraphQL API
• Reviewing API specifications before implementation
• Establishing shared API design standards

Design REST and GraphQL APIs by clarifying who will use them and how. Define data structures, errors, authentication, pagination, and versioning, then review examples to make the interface consistent and easier to use.

• Designing a new REST or GraphQL API
• Reviewing API specifications before implementation
• Defining shared API design standards for a team

Explore training workflows that reduce harmful model responses using a written set of principles. The skill covers self-critique, revised training examples, and RLAIF, reinforcement learning from AI feedback, with implementation examples and hardware guidance.

• Designing principles for model safety training
• Creating training examples through self-critique and revision
• Planning reinforcement learning with AI-rated responses

Review Google Cloud workloads against the security principles of the Well-Architected Framework. Identify gaps in access control, network protection, data handling, and security operations, then receive prioritized recommendations linked to relevant Google Cloud products.

• Reviewing security during Google Cloud architecture design
• Checking access permissions and network defenses
• Identifying gaps in data protection and security monitoring

Analyze a problem by separating fundamental facts from policies and untested assumptions. The skill produces a component breakdown, a constraint table, and a rebuilt solution, helping explain which inherited assumptions may be limiting the available options.

• Breaking down the causes of high costs
• Reviewing requirements inherited from past projects
• Reconsidering a design that has stalled

Explore training workflows that reduce harmful model responses using a written set of principles. The skill covers self-critique, revised training examples, and RLAIF, reinforcement learning from AI feedback, with implementation examples and hardware guidance.

• Designing principles for model safety training
• Creating training examples through self-critique and revision
• Planning reinforcement learning with AI-rated responses

Review prose in Quarto manuscript files for clutter, weak verbs, inconsistent voice, and unclear explanations using William Zinsser’s writing principles. Receive a separate Markdown report with section-based recommendations and reasons, while the source file remains unchanged.

• Finding wordy expressions in an academic manuscript
• Reviewing only the introduction
• Checking section openings and conclusions

[omh] Turn repeated lessons into written rules: extract repeated principles from skills, prompts, traces, reviews, and failures into reviewed rule candidates without auto-mutating guidance. Use when the user says: rules-distill, rules distill, distill rules, rule distillation, principle distill, skill principles, extract agent rules, turn traces into rules.

The English summary is being prepared. Showing the original description.

Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use `design-brief`.

The English summary is being prepared. Showing the original description.

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

The English summary is being prepared. Showing the original description.

Apply the seven principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity, unity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", "commitment and consistency", "shared identity", "in-group", "make my copy more persuasive", "increase trust", or "get more people to say yes". Also trigger when designing testimonial sections, crafting urgency messaging, or improving trust signals on landing pages. Covers the principles, when each applies, and ethical limits. For deal negotiation tactics, see negotiation. For viral word-of-mouth, see contagious.

The English summary is being prepared. Showing the original description.

Applies motion design principles to create emotionally-driven, technically sound animations and transitions. Provides timing, easing, choreography, and Disney animation principles adapted for UI. Use when creating animations, transitions, micro-interactions, loading states, page transitions, scroll-triggered effects, or any motion work. Works with CSS, Framer Motion, GSAP, Lottie, Spring, or any animation system.

The English summary is being prepared. Showing the original description.

Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.

The English summary is being prepared. Showing the original description.

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

The English summary is being prepared. Showing the original description.

Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.

The English summary is being prepared. Showing the original description.

Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.

The English summary is being prepared. Showing the original description.

SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length, use clean-code instead.

The English summary is being prepared. Showing the original description.

Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.

The English summary is being prepared. Showing the original description.

Use when persuasion principles have to be applied to a specific asset — reciprocity, scarcity, authority, social proof, liking, commitment, and unity mapped onto copy, a landing page, an email, or an ad, each with a hypothesis and a test plan. Trigger on 'marketing psychology', 'Cialdini', 'persuasion principles', 'how do I add urgency', 'make this more convincing', 'behavioral triggers for this page'. Also use when the user asks why people read the whole page and still do not buy. Not for — price framing and margin math, see `17-pricing-strategy-global`; building the offer itself, see `31-offer-design-global`; running the experiment properly, see `19-ab-test-setup-global`.

The English summary is being prepared. Showing the original description.

Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.

The English summary is being prepared. Showing the original description.

Mobile-specific UX principles - touch targets, hover-less doctrine, thumb zones, safe areas, gestures, mobile perf budgets. Cross-platform (web mobile, iOS, Android).

The English summary is being prepared. Showing the original description.

MANUAL-ONLY: challenge a product idea, design, PRD, or architecture from first principles. Use only when the user names this skill. Research first, then write a local review and PRD handoff.

The English summary is being prepared. Showing the original description.