「unit」の検索結果

Create a consistent spacing system based on a base unit with contextual application rules.

日本語の概要は準備中です。原文の説明を表示しています。

Find opportunities to add metrics and estimate numbers when exact data unavailable

日本語の概要は準備中です。原文の説明を表示しています。

Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

日本語の概要は準備中です。原文の説明を表示しています。

Generate editorial calendars for blogs with topic clusters, publishing schedules, content decay detection, freshness update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling. Plans monthly or quarterly calendars optimized for SEO topic authority and AI citation freshness requirements (30-day update cycles). Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".

日本語の概要は準備中です。原文の説明を表示しています。

Audit any domain for orphan blog pages, map internal links across all blog posts, generate keyword-backed interlinking briefs via DataForSEO, and produce a self-contained downloadable HTML report. Invoke with the target domain as the argument.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to set up automated daily promotion / marketing for their Claude Code skills — researching how top skills are promoted on marketplaces (ClawHub / openclaw / SkillsMP / agentskills.io), generating a per-skill marketing plan, auto-posting to X (Twitter) via xurl, and drafting community discussion posts (Reddit / HN / Discord). Triggers — "推广 skills", "营销 skills", "自动发推广", "每天自动推广", "skill marketing", "promote my skills", "/wjs-promoting-skills".

日本語の概要は準備中です。原文の説明を表示しています。

Generate unit tests for untested branches and edge cases. Use when coverage is low, CI flags gaps, or a release needs hardening. Not for integration/E2E suites, framework migrations, or fixing production bugs.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever you are reasoning about large-scale scientific projects, genomics, bioethics, data infrastructure, or long-term medical translation. Eric S. Lander (geneticist, Broad Institute, Human Genome Project) provides a framework for hypothesis-free discovery, structuring "big science," and treating biology as an information science. Reach for this when the user is discussing open science, collaborative ecosystems, CRISPR/gene editing ethics, managing massive datasets, or setting realistic timelines for technological breakthroughs. Apply his principles to avoid the "lone genius" myth, prevent overpromising, and build foundational infrastructure that serves the broader community.

日本語の概要は準備中です。原文の説明を表示しています。

Reach for this skill whenever Claude encounters situations involving supply chain innovation, B2B customer respect, community revitalization, vocational education, or navigating massive business crises. Apply the mental models of Diane Hendricks, co-founder of ABC Supply and building supplies billionaire, when users face decisions about strategic acquisitions, counter-cyclical expansion, or treating blue-collar workers as respected entrepreneurs. Use this skill to channel her 'fight or fold' resilience, her strict financial responsibility hierarchy, and her focus on solving the exact pain points you faced as a customer.

日本語の概要は準備中です。原文の説明を表示しています。

Applies the philosophical frameworks of Confucius (ancient Chinese philosopher, 551-479 BCE) to modern problems. Reach for this skill whenever the user is dealing with leadership, governance, team harmony, organizational culture, moral dilemmas, mentorship, or personal self-cultivation. It triggers on topics like building trust without micromanaging, resolving hierarchical conflicts, aligning actions with values, and creating systems based on virtue rather than strict punitive rules. Use this skill to evaluate character, design educational approaches, and foster long-term social harmony.

日本語の概要は準備中です。原文の説明を表示しています。

This skill channels the strategic thinking of Mark Zuckerberg, co-founder and CEO of Meta. Reach for this skill whenever the user is navigating rapid product iteration, scaling social platforms, open-source AI strategy, content moderation trade-offs, or long-term organizational management. It is highly effective for scenarios involving "The Hacker Way" (rapid prototyping), building community, handling intense public criticism, or deciding between open vs. closed ecosystems. Use this skill to apply his frameworks on decentralized testing, small group context sharing, and progressive AI integration, even if the user doesn't explicitly mention his name.

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned operations-assessment discipline that maps how work actually happens before anyone designs a system: floor-level interviews with the people who do the work, an inventory of every silo including spreadsheets and inboxes used as databases, friction quantified in the requester's own numbers, opportunities ranked by annual value against build complexity, and adoption watched for the thirty days after launch. Use when nobody can answer what to automate, when an operation needs auditing before a build, when tribal-knowledge and key-person risk has to surface, or when a shipped system is quietly being routed around. NOT FOR: deciding what to build and in what order once the map exists (use suede-ops-architecture); researching external customers rather than internal operators (use suede-customer-research); lead lifecycle, scoring, and CRM routing rules (use suede-revops); product instrumentation and dashboards (use suede-analytics); getting a new user to first value (use suede-onboarding).

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned operations-architecture discipline that fixes the shape of a system before anyone builds it: entity schema first, exactly one write path per entity, every unit of work routed to a deterministic automation, an AI agent, or a human decision, every existing tool marked absorb, keep, or kill, and the build sequenced into phases whose completion is proved by a command. Use when scoping an automation or agent build, deciding whether a workflow needs a model at all, consolidating a sprawling tool stack, designing the data model under a workflow, choosing a migration path off an old system, or ordering a build so nothing lands on a moving foundation. NOT FOR: executing a planned multi-file repo change (use suede-graph-flo-xr); coordinating parallel builders with file ownership (use suede-agent-teams); lead lifecycle, scoring, and CRM routing rules (use suede-revops); proving agent output quality against an eval set (use suede-ai-eval); reviewing the finished diff (use suede-code-review).

日本語の概要は準備中です。原文の説明を表示しています。

Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap/site-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.

日本語の概要は準備中です。原文の説明を表示しています。

Patterns for Rust testing in Axone CosmWasm contracts. Use when adding unit tests, integration tests, data-driven cases, or coverage-oriented test scenarios.

日本語の概要は準備中です。原文の説明を表示しています。

The social network for AI agents. Post, comment, upvote, and create communities.

日本語の概要は準備中です。原文の説明を表示しています。

Perform a comprehensive DRY (Don't Repeat Yourself) code review on a codebase. Identifies duplicated code, repeated logic, redundant patterns, and opportunities for abstraction. Use this skill whenever the user asks to review code for duplication, reduce repetition, apply DRY principles, refactor for reusability, find copy-pasted code, deduplicate logic, or audit code quality with a focus on redundancy. Also trigger when users say things like "clean up my code", "find repeated patterns", "too much boilerplate", "reduce code duplication", or "refactor for maintainability". Works on any language or framework.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to know if something works — the answer requires running code, not analyzing it. Output is a verdict backed by evidence: passed, failed, or broken. Primary triggers: 'run the tests', 'does X still work after my change?', 'did the merge break anything?', 'verify the fix worked', 'check if the endpoint returns X', 'confirm nothing regressed', 'run tests/unit/test_foo.py', 'let me know the results', 'make sure my changes didn't break anything'. Hard stops — do NOT use for: reviewing test code for quality/coverage gaps, debugging why test infrastructure/databases/seed scripts are misbehaving, writing or fixing tests, diagnosing root causes of unexpected behavior. The deciding question: is the user asking for the result of executing something, or asking for help understanding/analyzing/improving something? If it's the latter, use diagnose or review-code instead.

日本語の概要は準備中です。原文の説明を表示しています。

Normalize and collect complete Opportunity Solution Tree inputs before OST synthesis.

日本語の概要は準備中です。原文の説明を表示しています。

Select one target opportunity from an OST using evidence-based weighted scoring and tie-breakers.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the diff changes C, C++ or Objective-C, Rust unsafe blocks, Go unsafe or cgo, JNI, Python ctypes/cffi or C extensions, Swift unsafe pointers, C# unsafe or Marshal code, or a native plugin, parser or loader that sees untrusted bytes - bounds, integer overflow before allocation, unit confusion, lifetimes, uninitialized memory, format strings, FFI ownership and library search order

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing game code in C#, GDScript or C++ (Unity, Godot, Unreal, custom engines) - client vs server authority, RPC and packet validation, in-app purchases and economy, save and replay files, mod and script loading, secrets in client builds

日本語の概要は準備中です。原文の説明を表示しています。

Use when building a 2D web game with Phaser (3.x/4.x) or PixiJS 8 in TypeScript - framework vs renderer, Phaser scenes/game objects/arcade physics/groups as pools/scale manager/loader, scene shutdown cleanup, PixiJS 8 async init, Assets bundles, ticker units and destroy, and keeping rules in plain TS modules.

日本語の概要は準備中です。原文の説明を表示しています。