「bus」の検索結果

Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.

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

Use when a team wants to design, audit, or operate an AI Marketing OS — a Brand Hub source of truth, role-based AI projects for leader, content, design, performance, and knowledge, skill chains, ChatGPT plus Claude plus NotebookLM workflows, MCP connectors, a Notion or Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'set up our marketing AI system', 'Brand Hub', 'AI workflow for the team', 'MCP for ads data', 'how do I make AI actually useful for marketing'. Not for — one campaign brief, see `02-campaign-brief-global`; the weekly report, see `07-marketing-report-global`; the brand visual rules, see `46-brand-guideline-global`; the product context file, see `product-marketing-context-global`.

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

Use when a campaign needs its full design asset list before anyone opens a tool — asset type, dimensions, channel, quantity, priority, owner, deadline, and status, with deadlines counted backward from launch day on a T-14 to D+1 timeline plus a naming convention. Trigger on 'campaign asset list', 'what does the designer need', 'list the design files', 'creative asset plan', 'how many banners do we need', 'the designer keeps asking what to make'. Not for — the spec for one individual image, see `42-image-brief-global`; a slide sequence, see `43-carousel-brief-global`; an urgent mid-campaign swap, see `48-quick-visual-brief-global`; resizing an existing master, see `50-asset-resize-global`.

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

Use when raw data exists — Meta, Google, TikTok, GA4, Shopify, a CRM export, or a spreadsheet — and has to become insight and decisions: descriptive, diagnostic, predictive, and prescriptive layers, cuts by channel, campaign, creative, audience, and time, cohorts, and a decision log. Trigger on 'analyze this data', 'read these numbers for me', 'what does this export say', 'pull insight from GA4', 'cohort analysis', 'here is the spreadsheet'. Also use when the user pastes a table and asks what it means. Not for — diagnosing ad root cause, see `03-performance-eval-global`; writing the report a stakeholder reads, see `07-marketing-report-global`; auditing account setup, see `21-ads-audit-global`.

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

Use when the user needs PAID ad copy for Meta, Google, or TikTok — six variants across TOFU, MOFU, and BOFU using AIDA, PAS, and BAB, respecting each platform character limit and ad policy, with a dropshipping mode. Trigger on 'ad copy', 'write Facebook ads', 'TikTok ad copy', 'Google RSA headlines', 'primary text for this ad', 'my ad copy is not converting'. Also use when the user has a product page and asks what to run as an ad. Not for — organic social captions, see `37-social-caption-global`; spoken video lines, see `04-script-video-global`; approving copy already written, see `62-marketing-review-global`; the page the ad points at, see `12-landing-page-brief-global`.

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

Use when a NEW landing page, sales page, or single-product page has to be built — seven-section structure, one page one goal one CTA, copy per block, mobile-first rules, technical and speed requirements, tracking plan, A/B test plan, and a dropshipping single-product mode. Trigger on 'landing page brief', 'build a sales page', 'I need a landing page', 'brief for the dev', 'Shopify product page', 'what should go on the page'. Also use when ad traffic is ready and there is nowhere to send it. Not for — the ad copy pointing at the page, see `05-ad-copy-global`; the offer and its value stack, see `31-offer-design-global`; scoring a finished design, see `47-design-review-global`; coded email, see `49-html-email-template-global`.

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

Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes /atlas, or wants task-driven development.

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

Zero-config goal-to-tasks engine. Takes any goal (software, pentest, business, learning), runs adaptive discovery, generates a validated spec, parses into TaskMaster tasks, creates an implementation plan, and executes with built-in CDD verification. Use when user says "PRD", "product requirements", "I want to build", or any goal-driven phrase.

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

Translates Chinese resumes and business texts into professional English, and adapts personal experiences into compelling MBA application essays with strict adherence to prompts and word counts.

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

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.

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

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

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

Red Team persona for Business Logic and Auth manipulation. Generates and executes stateful fuzzing scripts (Playwright/Python) to test RBAC bypasses, BOLA/IDOR, race conditions, and complex multi-step transaction flaws.

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

Investigate requirements via atomic AC decomposition, actor/permission matrices, and truth-table edge cases; enforce User Story standards (scope fences, platform tags, toggles). Use when writing/reviewing Stories or AC with multi-condition logic, feature toggles, or market variants (VN/MY/SG).

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

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.

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

Apply core Effective Java patterns for robust, maintainable code. Use when applying SOLID principles, choosing between inheritance and composition, refactoring Java code smells, or reviewing class design.

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

Probe for hardcoded secrets, injection surfaces, unguarded routes, business logic flaws, and platform-specific weaknesses across backend (Node, Go, Java, Python, Rust), frontend (React, Angular, Vue), and mobile (iOS, Android, Flutter) codebases. Use when performing security audits, vulnerability scans, secrets detection, or penetration testing.

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

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.

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

Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only.

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

Use whenever the user asks to "humanize", "make this sound more human", "rewrite to avoid AI detection", "make this less AI-sounding", "add a human voice", or "write like a person". Also use when the user pastes text and asks why it reads as robotic, generic, flat, or AI-like, or when generating new text in a register where AI tells (em dashes, semicolons, hedges, banned vocabulary like "delve", "leverage", "robust") would damage credibility.

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

Create a repository-grounded AppSec threat model covering assets, trust boundaries, attackers, abuse paths, and mitigations. Use only for explicit threat-modeling requests, not general architecture or code review.

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

Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.

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

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

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

Azure Functions, Cosmos DB modeling, Service Bus patterns, Bicep templates

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

Write robust, portable shell scripts with proper error handling, argument parsing, and testing. Use when automating system tasks, building CI/CD scripts, or creating container entrypoints.

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