「technical」の検索結果

Access 20+ years of global financial data: equities, options, forex, crypto, commodities, economic indicators, and 50+ technical indicators.

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

Ensure every factual claim in a response is backed by verifiable evidence from the codebase, documentation, or external sources. Use when preparing technical documentation, code reviews, or any output where accuracy is non-negotiable.

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

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

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

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

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

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

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

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

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

Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.

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

Frontend UI design, critique, audit, polish. Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.

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

System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.

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

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

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

Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

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

Use for every progress update, status report, problem explanation, ETA, review, acceptance, or completion report to the operator/owner, especially when they ask “到哪了”, “什么问题”, “做了什么”, “结果呢”, “还要多久”, or “说人话”. Translate technical evidence into visible or operational outcomes before details.

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

Architecture decisions, trade-off analysis, and ADR authoring. Trigger when a significant technical decision needs to be made, documented, and owned — not when an implementation detail needs a choice.

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

Use when revising or reviewing scientific, technical, or academic manuscripts, proposals, abstracts, reports, or related writing for precision, concision, logical cohesion, citation support, evidence alignment, and objective scholarly tone.

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

When processing code review feedback (bot or human) before changing anything — triages, verifies and pushes back with technical reasoning — even when the user just says 'fix the comments'.

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

When co-authoring a PRD, design doc, RFC, decision doc, or technical spec — 3-stage flow (context → section-by-section → reader-test) — even if the user just says 'help me write this spec'.

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

Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.

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

[Planning] Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.

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

[Process] Use when the developer wants something explained or taught, or wants to know HOW TO REVIEW a change — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a teacher-and-coach review guide, high level first then detail: what was done, a VISUAL MAP (system flowchart, domain ERD, sequence diagrams), the user stories and business rules with their REAL test-case IDs, a REVIEW PATH naming which files to open first and in what order with an exit criterion per stage, the technical concepts needed to follow it, how it works, why THIS solution, every alternative option with pros/cons, the trade-offs accepted, the blast radius, HOW TO TEST AND DEMO the change, the developer's decision levers, and written challenge prompts that provoke the reader to pressure-test the work. Works at ANY scope — from one line of code to the whole project: it SIZES the target into a scope tier, DECOMPOSES a large one into understanding groups, BREAKS the work into tasks before the first deep read, and ACCUMULATES the report group by group on disk so a huge explanation stays complete instead of thinning out. Writes the full report to a single combined markdown file (plans/reports/understand-*.md) that opens with a detailed summary section — or delivers it in full in chat when Step 3 finds no git-ignored directory for it — and always summarizes it in chat. Regardless of coding level. Never interrogates, never quizzes, never blocks.

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

[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/test-code drift. A GENERATOR — it projects code + tests into a regenerable per-component view and NEVER authors business content. Modes generate|audit|sync. Per-mode procedure lives in references/{author,sync}.md.

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

[Documentation] Use when finding technical documentation for libraries, frameworks, repositories, or implementation topics.

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

[Code Quality] Use when the user asks to enhance documentation, add code comments, create API docs, improve technical documentation, document code, or update README files.

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