「design」の検索結果

Design consistent error handling across web, mobile, and React Native—central handlers, user-facing copy, retry, and logging.

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

Design lightweight CI quality gates—lint, test tiers, security scans, and merge policies. Use when setting up or improving pipelines without tying to one stack only.

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

"Optimize SQL query performance using EXPLAIN analysis, indexing strategies, and common anti-pattern fixes. Use this skill when the user needs to speed up slow queries, design indexes, fix N+1 problems, or optimize database performance — even if they say 'this query is slow', 'optimize our database', 'which indexes do we need', or 'our dashboard takes 30 seconds to load'.".

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

Guide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.

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

"Analyze and design pricing strategies including cost-plus, value-based, competitive, penetration, and skimming approaches with psychological pricing techniques. Use this skill when the user needs to set or change prices, evaluate pricing models, understand price elasticity, or apply psychological pricing — even if they say 'how much should we charge', 'are we priced right', or 'our margins are too low'.".

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

"Enterprise risk management (ERM) framework layer — integrates COSO ERM 2017 (five components, 20 principles), ISO 31000, three-lines model, risk appetite, risk heatmap, and key risk indicators (KRI) into a complete governance playbook covering structure through culture. Use for ERM implementation, risk-system build, risk mapping, risk-appetite statement drafting, three-lines setup, CRO role design, or Taiwan FSC corporate-governance evaluation response. Triggers: 『ERM 導入』『風險管理框架』『COSO』『風險地圖』『風險胃納』『KRI』『CRO 職責』『三道防線』『風險委員會』『ISO 31000』『風險熱圖』『風險治理』. For 師大／政大／陽交 EMBA risk-management/governance/audit cases. Complements Asgard `algo-risk-*` (Altman Z, Benford, credit, VaR) with the framework/governance layer. 獨董挑選/董事會組成/IPO 治理: use `biz-corporate-governance`.".

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

"SME and family-business management for Taiwan's industrial structure (98% SME, 70%+ family-controlled listed). Integrates four pillars: resource-constrained decision-making, family governance (Tagiuri-Davis three circles), four-layer succession, and professionalization. Use for sub-200-employee strategy, capital-constrained prioritization, family-vs-professional-manager conflict, founder handover, family-constitution design, or SME financing limits. Triggers: 『二代接班』『家族企業』『中小企業』『家族憲章』『家族辦公室』『傳承規劃』『小公司策略』『資源有限』『家族跟專業經理人』『三圓模型』『隱形冠軍』. For 成大 EMBA SME strategy, 政大 EMBA family-business succession, 逢甲 EMBA SME management cases. Fills Asgard gaps in resource-constrained strategy and Chinese-family governance.".

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

"Management accounting toolkit for internal decision support: ABC costing, variance analysis, transfer pricing, and responsibility accounting. Use for product profitability disputes, budget variance diagnosis, inter-division pricing design, and business-unit manager performance evaluation. Triggers: 『這個產品真的賺錢嗎』『成本分攤』『事業部之間怎麼算錢』『本月成本超支』『評核廠長績效』『內部轉撥』『ABC 作業成本』『差異分析』『責任中心』『管理會計』. For Taiwan EMBA cases, term reports, and management-decision simulations (台大／陽交／成大 財管必修).".

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

"Analyze supply chain operations using the SCOR model across Plan, Source, Make, Deliver, and Return processes. Use this skill when the user needs to optimize supply chain efficiency, evaluate supplier performance, improve logistics, or design an end-to-end supply chain strategy — even if they say 'our deliveries are slow', 'supply chain costs are too high', or 'we keep running out of stock'.".

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

"Corporate-governance practice playbook: board composition, three lines of defense, audit/compensation/nomination committee operations, independent-director governance, stakeholder communication, IPO governance upgrade, and family-business professionalization. Use for board-structure design, independent-director selection, three-lines implementation, IPO governance preparation, major governance incidents (fraud, scandal, insider trading), or family-business corporatization. Triggers: 『董事會組成』『獨董沒發揮功能』『三道防線』『上櫃治理補強』『家族法人化』『委員會分工』『ESG 治理』『審計委員會』『薪酬委員會』『提名委員會』. For Taiwan EMBA corporate-governance/finance/law/ESG cases. Focuses on listed-company and IPO practice; governance theory: use Asgard `grad-governance`; 9-box/繼任規劃/接班人才盤點: use `ops-talent-strategy`; COSO ERM/風險地圖/風險委員會運作: use `biz-erm`.".

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

"Apply Blue Ocean Strategy to create uncontested market space through value innovation. Use this skill when the user needs to differentiate beyond price competition, find new market opportunities, or redesign a product's value proposition using the Strategy Canvas and Four Actions Framework (Eliminate-Reduce-Raise-Create). Also use when the user says 'how do we stop competing on price', 'create a new category', or 'escape the red ocean'.".

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

"Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.".

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

"Design bundle pricing strategies using pure bundling, mixed bundling, and consumer surplus analysis. Use this skill when the user needs to set prices for product bundles, determine whether bundling increases profit, or analyze unbundling opportunities — even if they say 'should we bundle these products', 'bundle pricing', or 'package deal pricing'.".

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

"Design multi-objective e-commerce product ranking combining relevance, conversion, and business metrics. Use this skill when the user needs to build a product ranking system beyond text relevance, balance relevance with commercial objectives, or implement learning-to-rank — even if they say 'product sorting', 'search result ranking', or 'how to rank products'.".

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

"Design hybrid recommendation systems combining multiple strategies for improved accuracy. Use this skill when the user needs to overcome single-method limitations, combine collaborative and content-based filtering, or build a production recommendation pipeline — even if they say 'combine recommendation approaches', 'best recommendation architecture', or 'cold start plus personalization'.".

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

Design agent tools and CLI surfaces—schemas, naming, errors, idempotency, and discoverability for LLM callers. Use when defining tools for agents, SDKs, or AI-native CLIs.

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

Auto-activates when generating Product Requirements Prompt (PRP) documents from synthesized design outputs, providing structured templates and comprehensive implementation guidance.

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

Implement features with code, tests, and documentation. Use when building features from approved designs following TDD and project coding standards.

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

Write a durable feature spec before touching code. Reads the codebase map, reads related models/migrations to ask technical questions (not generic ones), then produces a structured spec doc in docs/specs/. Designed to pipeline with /implementation --issue N. Use before any feature implementation.

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

Phase 0 validation gate — problem framing, competitive analysis, feasibility, and a go/no-go checkpoint before committing to a feature. Use when evaluating whether an idea is worth building, before /story or /design. Trigger on "is this worth building", "validate this idea", "discovery", "should we build".

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

Design UI, build components, write Playwright E2E tests, run WCAG accessibility audits, and do visual review. Use when building or testing frontend/UI work. Trigger on "build a component", "frontend", "E2E test", "accessibility audit", "a11y", "visual review", "make this look good".

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

Design component architecture and module structure using established architectural patterns for clean, maintainable, and scalable systems.

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

Design data models with Pydantic schemas, comprehensive validation rules, type annotations, and relationship mappings.

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

Detects version drift between machine-readable law YAML files and the binding geldende wettekst on wetten.overheid.nl at the YAML's claimed valid_from. Catches the silent failure where authored content lags behind ingevoerde wijzigingen — a YAML dated 2025-01-01 still carrying pre-Stb.-X text. Activate as Step 0 of every regelrecht-stelselanalyse micro-cycle, before any YAML edit. Strict by design: no bypass, no normalization beyond whitespace within a single paragraph; the geldende wettekst is leading and is mirrored verbatim, including errata. Use proactively when starting a stelselanalyse cycle, before harvest/migrate/extend, or when user mentions "drift", "versie", "geldende tekst", or worries that a YAML may be stale relative to wetten.overheid.nl.

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