「design」の検索結果

Generalised autonomous optimisation loop — soft RLVR for any artifact a user can measure. Web runtime package: uses memory in this order: connector-backed, project-pack, none. Never assumes subprocess access or unrestricted local files. Use this skill whenever a user wants to iteratively improve an artifact — code, prompts, documents, configs, designs, content — by running structured experiments, evaluating results against a multi-dimensional rubric, and learning from each attempt. Triggers include: "optimise this", "keep improving until it's good", "run experiments on", "autoresearch", "iterate on this overnight", "try different approaches and pick the best", or any request implying repeated evaluate-and-improve cycles.

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

Spring Boot coding conventions: REST controller design, service layer, dependency injection, configuration, DTO patterns, exception handling, and Bean Validation. Apply on any Spring Boot project. Works alongside spring-boot-plugin:spring-data-jpa for persistence and java-foundation:java-conventions for domain objects. Use this skill to: - Structure REST endpoints with @RestController, proper HTTP semantics, and DTO mapping. - Enforce constructor injection and @ConfigurationProperties over @Value on fields. - Write @Service classes with transactional boundaries at the right layer. - Handle errors consistently with @RestControllerAdvice and ProblemDetail (RFC 9457). Do NOT use this skill for: - JPA entity and repository patterns — see spring-boot-plugin:spring-data-jpa. - Spring Security configuration — see the security phase injection in stack.md. - Build tool configuration — see java-foundation:build-tooling.

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

Application and library conventions for plain Python projects (no web framework): src/ package layout, CLI tooling (argparse/click/typer), configuration management (pydantic-settings), logging setup, module design, entry points, and packaging conventions. Activated automatically by python-plugin/stack.md as a convention skill for the development phase. Use this skill to: - Organise Python application code in a src/ layout with proper package structure. - Build CLI tools with argparse, click, or typer and register them as console scripts. - Manage configuration from environment variables using pydantic-settings. - Set up structured logging for production-grade applications. - Package a Python project correctly with pyproject.toml. Do NOT use this skill for: - Language idioms (type hints, dataclasses, enums, match/case) — see python-foundation:python-conventions. - Package manager commands (ruff, mypy, pip/poetry/uv) — see python-foundation:python-tooling. - Testing patterns — see python-foundation:pytest-testing. - Web framework patterns (Django/FastAPI/Flask) — see those framework plugin skills.

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

Node.js backend conventions: project layout, configuration, logging, routing, and error handling patterns. Apply when implementing or modifying Node.js backend code in projects matching the nodejs stack profile. Use this skill to: - Pick conventional file/folder structure for a new module. - Wire configuration through env vars correctly. - Use the project's existing logger style. - Implement error handling that matches the framework (Express/Fastify/Koa). - Follow async/await patterns consistently. Do NOT use this skill for: - Frontend code (React/Vue/RN have their own conventions). - NestJS-specific patterns (decorators, DI, modules) — nest-plugin owns those. - Database schema design (call out as a sub-task; npm-patterns covers package management, not DB).

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

NestJS decorator usage: built-in route/param/class decorators, custom decorators via `createParamDecorator` and `SetMetadata`, metadata reflection via `Reflector`. Apply when designing controllers, guards, interceptors, or custom decorators. Use this skill to: - Pick the right built-in decorator for routes, params, and DI. - Compose decorators (`@UseGuards(A, B) @UseInterceptors(C)`). - Build custom param decorators (e.g., `@CurrentUser()`). - Use metadata for role-based logic (Reflector + SetMetadata). - Avoid common decorator mistakes. Do NOT use this skill for: - General module/DI patterns (see nest-conventions). - GraphQL-specific decorators (see nest-advanced). - ORM entity decorators (see nest-data-layer).

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

TypeScript discipline for any JavaScript/TypeScript project (frontend + backend): strict mode, type design, generics, narrowing, error types, module resolution, tsconfig hygiene. Apply when the project has `tsconfig.json` and `typescript` in devDependencies. Stack-agnostic — referenced by every JS/TS framework plugin in the marketplace. Use this skill to: - Write types that catch bugs at compile time, not runtime. - Use generics, conditional types, and discriminated unions correctly. - Avoid `any`, `unknown`, and unsafe casts. - Match the project's tsconfig strictness level. - Type third-party libraries (with @types/* or declaration files). Do NOT use this skill for: - Plain JavaScript projects (no tsconfig.json). - Framework-specific type idioms (React component props, Vue defineProps, Angular signals — those live in framework plugins' own conventions skills). - tRPC/Zod runtime-validation specifics — handled by validation libs at the boundary.

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

Modern C# idioms for any .NET project (C# 10+, .NET 6+): nullable reference types, records, readonly structs, primary constructors, pattern matching, async/await with CancellationToken, IDisposable/IAsyncDisposable, file-scoped namespaces, var usage, naming conventions (PascalCase members, _camelCase fields, I-prefixed interfaces), and class design rules. Apply whenever the project is a .NET 6+ project. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write self-documenting immutable value types with records and readonly structs. - Handle nullable reference types explicitly to eliminate NullReferenceException at compile time. - Implement async/await correctly with CancellationToken propagation and ConfigureAwait(false) in libraries. - Dispose unmanaged resources correctly via IDisposable / IAsyncDisposable and using statements. - Apply C# pattern matching (switch expressions, property patterns, list patterns) for cleaner branching logic. Do NOT use this skill for: - Framework-specific idioms (ASP.NET Core controllers, minimal APIs, EF Core — those live in aspnet-core-plugin skills). - Build tooling (dotnet CLI, NuGet, csproj) — see csharp-foundation:dotnet-tooling. - Testing patterns — see csharp-foundation:dotnet-testing.

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

应用从 AI for Everyone 蒸馏出的「数据飞轮 — AI产品自我强化的增长引擎」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to data-flywheel.

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

应用从 AI for Everyone 蒸馏出的「迭代而非完美 — AI产品的渐进式改进」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to iterate-not-perfect.

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

应用从 AI for Everyone 蒸馏出的「不等完美数据 — 先用起来再迭代」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to dont-wait-perfect-data.

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

应用从 AI for Everyone 蒸馏出的「ML项目流程 — 收集→训练→部署→迭代」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ml-workflow.

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

应用从 AI for Everyone 蒸馏出的「不为数据而收购 — 数据投资的价值验证原则」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to dont-acquire-for-data.

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

应用从 AI for Everyone 蒸馏出的「ML产出软件,DS产出洞察 — 项目类型判定框架」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ml-vs-ds.

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

应用从 AI for Everyone 蒸馏出的「AI价值驱动三途径 — 降本/增收/新业务」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to three-value-drivers.

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

应用从 AI for Everyone 蒸馏出的「从小处着手+寻找伙伴 — AI入门的行动原则」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to start-small-find-partner.

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

应用从 AI for Everyone 蒸馏出的「AI转型五步指南 — 组织变革路线图」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-transformation-playbook.

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

应用从 AI for Everyone 蒸馏出的「训练集/测试集分离 — AI的'科学方法」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to train-test-split.

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

应用从 AI for Everyone 蒸馏出的「AI战略护城河 — 用AI构建可持续竞争优势」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-strategy-moat.

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

应用从 AI for Everyone 蒸馏出的「AI团队构建 — 打造高效AI团队的角色与协作」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-team-building.

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

应用从 AI for Everyone 蒸馏出的「统一数据仓库 — AI的数据基础设施」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to unified-data-warehouse.

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

应用从 AI for Everyone 蒸馏出的「分层AI培训 — 高管/经理/工程师的差异化学习」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to role-tiered-training.

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

应用从 AI for Everyone 蒸馏出的「AI流水线 — 多组件串联的系统设计模式」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-pipeline.

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

应用从 AI for Everyone 蒸馏出的「试点势能飞轮 — 先求成功再求价值」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to pilot-momentum-flywheel.

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

应用从 AI for Everyone 蒸馏出的「统计化验收标准 — 不追求100%准确」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to statistical-acceptance.

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