「dire」の検索結果

Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.

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

Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes.

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

Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.

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

Use when a PERSONAL brand — founder, coach, or creator — needs a 12-month strategy: niche selection with Ikigai and a 3x3 matrix, positioning statement, a three-chapter story arc, four content pillars with 28 topics, a five-stage authority ladder, and a Q1 to Q4 growth plan. Trigger on 'personal brand strategy', 'founder brand plan', 'coach positioning', 'creator strategy', 'what niche should I own', 'I post constantly and nothing compounds'. Also use when the user has followers and no direction. Not for — a company brand, see `58-positioning-global` and `00-marketing-plan-global`; the context file this reads first, see `22-personal-brand-context-global`; turning it into revenue, see `27-personal-brand-monetize-global`.

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

Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline directions. Trigger on 'positioning', 'positioning statement', 'what makes us different', 'USP', 'why should customers choose us over them', 'we sound the same as everyone else'. Also use when the user can list features but not a reason to pick them. Not for — competitor teardown research, see `08-competitor-research-global`; how the brand sounds in writing, see `35-brand-voice-global`; the offer and its value stack, see `31-offer-design-global`; the launch built on it, see `59-go-to-market-global`.

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

Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.

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

Use when someone outside the marketing team has to film — a customer for UGC, an employee for EGC, or a paid creator or KOC — and needs a brief: talking points, shooting guide, do and do-not list, usage rights, deliverables, and batch management. Trigger on 'UGC brief', 'creator brief', 'KOC brief', 'brief for employee videos', 'what do I tell the influencer', 'we hired a creator to film'. Also use when the user asks how to get customers to make videos for the brand. Not for — a script the team writes and shoots itself, see `04-script-video-global`; edit direction for footage already shot, see `44-video-editor-brief-global`; posting inside communities, see `38-community-seeding-global`.

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

Use when a multi-slide carousel is needed for Instagram, Facebook, or LinkedIn — a narrative arc with the hook on slide one, value through the middle, CTA on the last, headline, body, visual direction, and background per slide, plus an HTML preview to approve the concept before production. Trigger on 'carousel brief', 'make a carousel', 'turn this into slides', 'LinkedIn carousel', 'slide by slide breakdown', 'preview the carousel first'. Not for — a single static image, see `42-image-brief-global`; the caption posted with it, see `37-social-caption-global`; production steps inside Canva or Figma, see `45-design-tool-brief-global`; scoring the finished slides, see `47-design-review-global`.

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

Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.

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

Use when ONE specific piece of content needs a brief before anyone writes — placement, angle plus the source insight behind it, key message, three hook options, CTA, format, brand voice reference, visual direction, and distribution. Trigger on 'content brief', 'brief for this post', 'brief a writer', 'what angle should this take', 'brief for the LinkedIn post', 'give the freelancer something to work from'. Also use when the user has a topic and no idea what to actually say about it. Not for — the month schedule of what posts when, see `01-content-calendar-global`; the finished caption text, see `37-social-caption-global`; a spoken video script, see `04-script-video-global`; the image spec, see `42-image-brief-global`.

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

针对问答或代码执行请求，严格仅输出核心答案或运行结果，不包含任何解释、背景、推理过程或引导性文字。

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

Generates a Python CLI tool for bidirectional conversion between 4-byte floating-point numbers and hexadecimal memory representations, featuring a continuous loop and robust input parsing.

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

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

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

Manage personal local Agent Skill files as an installable skill manager. Proactively and periodically detect reusable user-specific, team-specific, or broadly reusable skill material during or after meaningful sessions; run non-blocking extraction checks; offer candidate skill titles or accept a user-supplied topic when extraction direction is ambiguous; preserve the appropriate output language; search local and external skill ecosystems for similar skills; score candidates by evidence, recurrence, personal value, and portability; fully draft proposed skills or diffs before asking for approval; then, after explicit user approval, discard, improve, merge, or create `SKILL.md` folders.

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

Use when a user wants Codex to directly operate PowerPoint and reconstruct an entire reference image as editable PowerPoint objects while preserving its full layout, labels, connectors, and visual relationships. Do not use for paper-to-deck generation or VBA-only output.

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

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

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

Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /caveman-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.

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

Guide ethical customer discovery and research synthesis, distinguishing direct observations from inferences, preventing leading interview questions, and tracking quote-to-insight provenance. (triggers: `product customer discovery`, `product research synthesis`)

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

Structure Python backends with explicit dependency direction, ports/adapters, and runtime boundaries. Use when shaping project layout, clean architecture, service boundaries, dependency injection, report rendering boundaries, or transport separation in Python.

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

Implement Pages Router data fetching with getServerSideProps, getStaticProps, and API routes in Next.js legacy projects. Use when working in a pages/ directory project, adding SSR/SSG data fetching, or creating API routes.

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

Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.

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

Organize Android strings, drawables, fonts, themes, localization, and concrete resource-backed Compose values such as MaterialTheme colors. Use for resource declarations and their direct UI lookup; defer design-system token architecture, network image loading, lint-rule configuration, and general Compose implementation.

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

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

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