4,505 件 ・ 関連度順
概要と使いどころ
After any significant code change — new feature, API modification, config change, or architectural refactor — run this skill to identify which documentation files are now stale and update them. Keeps docs and code from drifting apart.
日本語の概要は準備中です。原文の説明を表示しています。
Implement bounded features and fixes in existing or new mini-program codebases while preserving repository rules, user-owned changes, approved behavior, assets, framework conventions, and evidence boundaries. Use when users ask to write or modify mini-program code, implement a confirmed specification or architecture, add a scoped feature, remove behavior semantically, update internal documentation required by a change, or carry out a well-defined small fix that does not require root-cause investigation. Establishes a baseline and change boundary, applies test-driven small steps, distinguishes source from generators and build artifacts, verifies the affected contract, and never reports source completion as device validation, formal acceptance, upload, or release.
日本語の概要は準備中です。原文の説明を表示しています。
Convert a vague mini-program idea, feature request, or partially documented product into an evidence-calibrated product specification with target users, core problem, version-one scope, main and exception flows, page responsibilities, state matrices, and testable acceptance criteria. Use when users ask to define an MVP, clarify requirements, organize product flows, specify page behavior, resolve ambiguous product states, or prepare a stable handoff before architecture or implementation. Separates facts, user decisions, assumptions, unknowns, and future ideas; never invents product logic merely to complete a screen or technical plan.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate evidence-first engineering for WeChat and other mini programs from a vague idea or existing repository through project discovery, product specification, architecture, implementation, debugging, device adaptation, verification, and release readiness. Use when users ask to build a mini program from zero to one, take over an existing mini-program project, deliver a cross-stage feature, diagnose project status, coordinate development and testing, or judge whether a mini program is ready to upload or release. Enforces fact discovery, change boundaries, stage gates, evidence-calibrated status, sensitive-information redaction, and continuity after side questions.
日本語の概要は準備中です。原文の説明を表示しています。
Design a developmental band system mapping student growth from early childhood through upper secondary. Use when building competency-based curriculum architecture for a school or programme.
日本語の概要は準備中です。原文の説明を表示しています。
Map knowledge components and skill hierarchies for a cognitive tutoring system or adaptive learning platform. Use when designing intelligent tutoring software or skill-based mastery systems.
日本語の概要は準備中です。原文の説明を表示しています。
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change"
日本語の概要は準備中です。原文の説明を表示しています。
Writes an architecture decision record (ADR) for a decision the team has already reached: the context, the options weighed, the choice and its consequences. Use when the user says "record this decision", "write an ADR", "we decided X, capture it", or asks to document a technical choice already made. Not for making the decision itself or for tracking the work it leads to.
日本語の概要は準備中です。原文の説明を表示しています。
LLMOps Architect: Run LLM features in production: model routing, evals, observability, caching, cost, safety.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-chain & L2 Architect: Chain selection, rollups, bridges and cross-chain messaging with their trust assumptions.
日本語の概要は準備中です。原文の説明を表示しています。
Smart Contract Systems Architect: Contract system design: modules, upgradeability, access control, storage, audit readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Web3 Infrastructure Architect: Indexers, RPC, wallets, account abstraction, key management and off-chain services.
日本語の概要は準備中です。原文の説明を表示しています。
DeFi Protocol Architect: Mechanism design for AMMs, lending, vaults and derivatives: oracles, liquidations, attack surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow Automation Architect: Automate business processes: triggers, queues, retries, approvals, n8n vs Temporal vs code.
日本語の概要は準備中です。原文の説明を表示しています。
AI x Web3 Architect: Autonomous agents that hold wallets: smart accounts, spend limits, intents, agent payments.
日本語の概要は準備中です。原文の説明を表示しています。
RAG & Knowledge Architect: Retrieval systems: ingestion, chunking, embeddings, hybrid search, reranking, evals.
日本語の概要は準備中です。原文の説明を表示しています。
AI Agent Architect: Design agent systems: single vs multi-agent, tools and MCP, memory, guardrails, evals.
日本語の概要は準備中です。原文の説明を表示しています。
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
日本語の概要は準備中です。原文の説明を表示しています。
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report
日本語の概要は準備中です。原文の説明を表示しています。
Build, revise, audit, or rebut a research manuscript from Harness Research evidence. Use for paper intake, related-work research, claim and citation control, section architecture, LaTeX patching, figure planning, reviewer response, or final manuscript hardening when the workspace contains Harness research artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Universal context persistence across sessions. Auto-saves decisions, conventions, and progress to .rune/ files. Loads state at session start. Use when any skill makes architectural decisions or establishes patterns that must survive session boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Performance regression gate. Detects N+1 queries, sync-in-async, missing indexes, memory leaks, and bundle bloat before they reach production. Ranks findings by Cost Impact Hierarchy (architecture > data transfer > compute > DB > caching) so fix priority maps to actual unit-cost reduction.
日本語の概要は準備中です。原文の説明を表示しています。