「concrete」の検索結果

Build an evidence-backed working model of an existing codebase. Use when you must orient in a large or unfamiliar repository; explain architecture or a subsystem; trace a request, runtime, control, or data flow for a concrete question or bug; analyze a branch, commit, diff, or pull request for behavioral impact and blast radius; or assess AI-generated or changed code against requirements, contracts, invariants, tests, and runtime evidence. Default to read-only investigation. Do not trigger only because a coding task touches an existing repository; use when understanding or verification is the requested outcome or a substantial prerequisite.

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

Continuous environmental scanning across six PESTEL categories — Political, Economic, Social, Technological, Environmental, Legal. Not a one-time analysis but an ongoing radar. Three modes. Diagnostic mode runs a full scan and prioritises forces by impact, speed, and reversibility. Review mode checks the watch list monthly for movement and new signals. Alert mode defines concrete monitoring triggers for each top force. Use whenever someone wants to understand external forces acting on their business, assess macro risk, prepare for planning, or check whether the world has moved since last time they looked. Connects to the strategy map (forces act on the chain) and Wardley Map (forces drive component evolution). Based on practice by Eterdis (eterdis.com).

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

Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).

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

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

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

ADHD-friendly output shaping for subagent responses. Lead with the next action, number multi-step tasks, end with one concrete next step, suppress tangents, restate state across turns, give specific time estimates, make wins visible, matter-of-fact errors, cap visible lists to 5, no preamble or closers. Loaded by genin, jonin, anbu, tokubetsu-jonin, and chunin when shaping final responses.

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

Evaluate, introduce, or refactor persistence abstractions when direct Eloquent is insufficient. Use for repository requests, complex aggregate reconstruction, or multiple persistence implementations; reject CRUD wrappers without a concrete benefit.

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

Review skills in any project using a dual-axis method: (1) deterministic code-based checks (structure, scripts, tests, execution safety) and (2) LLM deep review findings. Use when you need reproducible quality scoring for `skills/*/SKILL.md`, want to gate merges with a score threshold (for example 90+), or need concrete improvement items for low-scoring skills. Works across projects via --project-root.

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

Concrete remediation proposal with Safe Harbour confidence — version bump, inline as first-party code, patch, workaround, or advisory. Use when applying a fix for a triaged CVE, evaluating fix-type trade-offs across registry / source / distro patches, producing rollback-safe manifest edits with dry-run verification, or generating a CycloneDX SBOM after the fix lands.

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

Render a Template + data + Style into a final artifact in one of HTML, PDF, PNG, SVG or PPTX. Use whenever the user asks for a concrete deliverable like "make me a poster", "render a card", "give me a one-pager".

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

How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game Critic)? Who does which subtask? What does a development chain (concept → backend → frontend → polish → test) look like? How do you write a Game Design Document / KONZEPT.md? How do several (AI) agents divide up a game? Also trigger on "plan a new game", "create Game Design Document", "which roles do I need for my game", "development workflow for a game", "who tests the game", "structure a game idea", "Roblox genre/monetization".

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

Explain a stack trace or error message and suggest concrete fixes.

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

Coach German writing and conversation with minimal corrections, persistent root-cause mistake tracking (FehlerDNA), mistake-based spaced repetition with a new sentence every time, roleplay whose words return in spaced reviews, continuing preparation for real-life goals across sessions, and an honest progress profile. Use for German correction, personalized review, vocabulary, progress, roleplay, or preparation for an interview, presentation, appointment, or other concrete event; do not use for translation-only requests without learning or feedback.

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

Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.

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

Teach a micro-task in the style of the Feynman Technique. Start with a small concrete observation or action, explain the underlying concept from what the learner sees, then walk the learner step-by-step through the task. Before marking the micro-task done, require the learner to explain the underlying concept back in their own words; correct any misunderstanding before advancing.

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

Use when a user provides a GitHub URL and the planner needs to converge that repo plus the user's goal into a concrete project blueprint for later execution. This skill handles GitHub-input project intake, Phase 1 intent convergence, and downstream project handoff structure. It does not generate teaching material packages.

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

Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.

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

Build and run the owner's self-branding system in a structured way across LinkedIn, Substack, dev.to, X, profile rewrites, recurring series, and comment strategy. Use when the owner asks for positioning, a branding plan, profile updates, content drafts, a publishing sequence, comment ideas, or help maintaining a consistent public voice. Optimize for operator credibility: specific experience, defensible numbers, concrete artifacts, and category ownership.

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

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

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

Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.

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

Choose and compare cloud design patterns for distributed systems. Use when reviewing architecture, selecting workload patterns, or mapping reliability, performance, messaging, security, and migration concerns to concrete design options.

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

Scope the real change surface before editing. Use when planning a feature, bugfix, refactor, or review and you need a concrete map of likely touch points, dependencies, tests, and nearby risks.

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

Helps find, inspect, and compare .NET project templates. Resolves natural-language project descriptions to ranked template matches with pre-filled parameters. USE FOR: finding the right dotnet new template for a task, comparing templates side by side, inspecting template parameters and constraints, understanding what a template produces before creating a project, resolving intent like "web API with auth" to concrete template + parameters. DO NOT USE FOR: actually creating projects (use template-instantiation), authoring custom templates (use template-authoring), MSBuild or build issues (use dotnet-msbuild plugin), NuGet package management unrelated to template packages.

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

Catalog of MSBuild anti-patterns with detection rules and fix recipes. Only activate in MSBuild/.NET build context. USE FOR: reviewing, auditing, or cleaning up .csproj, .vbproj, .fsproj, .props, .targets, or .proj files. Each anti-pattern has a symptom, explanation, and concrete BAD→GOOD transformation. Covers Exec-instead-of-built-in-task, unquoted conditions, hardcoded paths, restating SDK defaults, scattered package versions, and more. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake, etc.), project migration to SDK-style (use msbuild-modernization).

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

Improve AI application with evaluation-driven development. Define eval criteria, instrument the application, build golden datasets, observe and evaluate application runs, analyze results, and produce a concrete action plan for improvements. ALWAYS USE THIS SKILL when the user asks to set up QA, add tests, add evals, evaluate, benchmark, fix wrong behaviors, improve quality, or do quality assurance for any Python project that calls an LLM model.

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