2,384 件 ・ 関連度順
概要と使いどころ
Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
日本語の概要は準備中です。原文の説明を表示しています。
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update OpenClaw public-page composition for websites, landing pages, content pages, ecosystem pages, and campaigns. Use for page structure, navigation, responsive layout, media, SEO presentation, or public-site visual polish.
日本語の概要は準備中です。原文の説明を表示しています。
Structured code review through the shared OpenClaw agent-skills installation.
日本語の概要は準備中です。原文の説明を表示しています。
Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare fundraising financial materials — investor model, data room financial docs, cap table, and use-of-funds narrative. Use when asked to "prepare for Series A", "build our investor model", or "what financials do investors want".
日本語の概要は準備中です。原文の説明を表示しています。
Write API reference documentation for an endpoint or SDK method. Use when asked to "document this endpoint", "write API reference docs", or "document this SDK method".
日本語の概要は準備中です。原文の説明を表示しています。
Survey documentation coverage across an API or SDK — find undocumented endpoints and gaps. Use when asked "what is undocumented", "find docs coverage gaps", or "survey our API documentation".
日本語の概要は準備中です。原文の説明を表示しています。
Survey corporate documents — articles, bylaws, cap table, board resolutions. Use when asked to "survey our corporate documents", "check cap table hygiene", or "what governance docs exist".
日本語の概要は準備中です。原文の説明を表示しています。
User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.
日本語の概要は準備中です。原文の説明を表示しています。
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".
日本語の概要は準備中です。原文の説明を表示しています。
Survey legal artifacts for audit readiness. Use when asked "are we audit ready", "what legal artifacts exist", or "survey our legal docs".
日本語の概要は準備中です。原文の説明を表示しています。
Internal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".
日本語の概要は準備中です。原文の説明を表示しています。
Turn Markdown outlines, notes, docs, or plans into an interactive mind map — a single self-contained HTML file that opens offline anywhere (markmap.js, white-on-dark, zoom/expand/export toolbar, search that keeps matches in context). Use whenever the user asks for a mind map, markmap, or concept map, wants to visualize or diagram the structure of a document or topic, summarize notes as a navigable tree, make an outline clickable or explorable, or embed such a map in Streamlit — even when they don't literally say 'mind map'.
日本語の概要は準備中です。原文の説明を表示しています。
Remove telltale signs of AI-generated "slop" writing. Use when polishing READMEs, docs, marketing copy, or public-facing text, or when text "sounds like ChatGPT".
日本語の概要は準備中です。原文の説明を表示しています。
Generates complete construction documentation packages — BOM, installation sequences, commissioning checklists, and O&M manuals — from verified engineering designs.
日本語の概要は準備中です。原文の説明を表示しています。
Write a Gherkin story file to docs/stories/ for a feature. The story IS the spec. No intermediate PROBLEM/SPEC/PLAN/TASKS artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Author and manage Architecture Decision Records (ADRs) in docs/specs/. Use when a significant architectural decision needs to be documented.
日本語の概要は準備中です。原文の説明を表示しています。