3,506 件 ・ 関連度順
概要と使いどころ
Use when designing, reviewing, refactoring, or enforcing Angular application architecture with isolated lazy features, eager core/layout, reusable ui/pattern architecture building blocks, one-way dependency graphs, eslint-plugin-boundaries rules, or folder placement decisions. This skill takes precedence over angular-developer when architecture rules conflict with general Angular advice.
日本語の概要は準備中です。原文の説明を表示しています。
Critically review a resume/CV against ATS (applicant tracking system) parsing rules, recruiter skim patterns, and keyword alignment with a target job description. Use when the user asks to "review my resume/CV", "check my resume against this job ad", "will this pass ATS", or shares a resume file (.docx/.pdf/.md) for feedback. Provides scored, prioritised, critical feedback — not a rewrite.
日本語の概要は準備中です。原文の説明を表示しています。
Core skill activation protocol - establishes mandatory workflows for finding and applying skills before any task
日本語の概要は準備中です。原文の説明を表示しています。
Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods.
日本語の概要は準備中です。原文の説明を表示しています。
Discover B2B leads from Reddit using AI-powered lead scoring via reddapi.dev Leads API. Finds high-intent signals, scores them 0-100, and classifies by lead type (pain_point, solution_request, complaint, feature_request, comparison). Perfect for competitor poaching, pain point discovery, and sales prospecting.
日本語の概要は準備中です。原文の説明を表示しています。
Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a vague "what should we do about X" into a scored decision - explicit actions, an explicit unknown, an explicit prior, and one utility scale - then picks by maximum expected utility and checks the result for framing effects. Use when facing a choice between options under uncertainty, when a decision has stalled in circular debate, when someone asks "should we do A or B", or before writing any decision record, strategy memo, or roadmap commitment.
日本語の概要は準備中です。原文の説明を表示しています。
Validates a plan before committing to it - checks whether the ranking survives the assumptions, finds the most likely way it fails, and makes the trade-offs explicit via a Pareto frontier instead of an invented single score. Use before a launch, price change, migration, infrastructure change or major commitment, when running a premortem, when two objectives conflict, or when a decision depends on an assumption nobody has tested.
日本語の概要は準備中です。原文の説明を表示しています。
FiveM RP server engineering for QBCore, ESX.
日本語の概要は準備中です。原文の説明を表示しています。
Fastest private buses (5-6h core, 6-8h w/ borders).
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in ZCode with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in Claude Code with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need blast-radius analysis, dependency graphs, cross-repo impact, breaking-change diff, or architectural overview of .NET workspaces. Keywords: blast radius, dependency graph, impact analysis, cross-repo, call graph, endpoint map, EF Core lineage, breaking change, daemon, reindex.
日本語の概要は準備中です。原文の説明を表示しています。
Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow, apps freeze, browser or MCP tool calls time out, load exceeds the core count, or before and after any UI/UX/performance test run. Includes the L0–L4 optimisation scale and the test-hygiene contract.
日本語の概要は準備中です。原文の説明を表示しています。
Deep multi-pass codebase audit — orchestrates project-analysis-core plus the framework-specific project-analysis-*; explicit request only. Single-pass scan → project-analyzer.
日本語の概要は準備中です。原文の説明を表示しています。
Single-pass tech-stack detection with an agents/evidence/analysis/ write-up; explicit request only. Deep multi-pass audit → universal-project-analysis. Raw primitives → project-analysis-core.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize prediction-pool tips (kicktipp etc.): rules + multi-book consensus odds → expected-points-max answer for every question, scores AND bonus. Triggers 'optimize my pool tips', 'predict'.
日本語の概要は準備中です。原文の説明を表示しています。
Raw discovery primitives — project discovery, version resolution, docs loading, architecture mapping, execution flow. Called by `universal-project-analysis`. Single-pass scan → `project-analyzer`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a security-maturity scorecard / posture assessment of a module — category ratings with evidence, not a vulnerability hunt. Also on 'wie sicher ist dieses Modul aufgestellt?'
日本語の概要は準備中です。原文の説明を表示しています。
Use before committing to a heavy or irreversible plan — imagine it's 6 months later and this failed; enumerate why, score each mode, derive early-warning signals and preventive guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adjudicating an operational go/no-go from typed evidence — a readiness enum with an explicit floor where one red is not-ready, unknown is never green, and no score can average a red away.
日本語の概要は準備中です。原文の説明を表示しています。
Use to consolidate multiple already-run judge verdicts into one report — consensus, conflicts, must-fix/should-fix with per-judge provenance. Consume-only, no opaque score, never auto-gates.
日本語の概要は準備中です。原文の説明を表示しています。