778 件 ・ 関連度順
概要と使いどころ
Govern Asphalt-Codex-Skills-5 as a PFC 5.0-only asphalt-mixture package, enforcing version purity, external fistPkg boundaries, portable assets, validation, and release hygiene.
日本語の概要は準備中です。原文の説明を表示しています。
Unwraps hard-wrapped markdown files so that each sentence ends with a newline instead of mid-sentence line breaks. Joins continuation lines within a paragraph into single lines, then re-breaks at sentence boundaries (period, question mark, exclamation point). Preserves blank lines, headings, fenced code blocks, block quotes, and list items. Use when asked to unwrap text, fix line breaks, reflow sentences, or clean up hard-wrapped markdown or .qmd files.
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight design smell review for modules and APIs—coupling, cohesion, naming, boundaries, and unnecessary complexity. Use before large refactors or when code feels hard to change. Complements gstack/review (diff-focused).
日本語の概要は準備中です。原文の説明を表示しています。
Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files.
日本語の概要は準備中です。原文の説明を表示しています。
Design API and module boundaries with clear contracts, error semantics, pagination, and additive compatibility. Use before implementing REST/GraphQL endpoints, SDKs, or public module APIs.
日本語の概要は準備中です。原文の説明を表示しています。
"Conduct Van Westendorp Price Sensitivity Meter analysis to identify acceptable price ranges. Use this skill when the user needs to determine price boundaries for a new product, find the optimal and indifference price points, or survey-based pricing research — even if they say 'what should we charge', 'price sensitivity survey', or 'acceptable price range'.".
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive integration tests for component interactions, workflows, and system boundaries. Use for testing API endpoints, database operations, and multi-component flows.
日本語の概要は準備中です。原文の説明を表示しています。
SAML SSO assertion attack playbook. Use when testing signature validation, assertion wrapping, audience restrictions, ACS handling, XML trust boundaries, and enterprise SSO flaws.
日本語の概要は準備中です。原文の説明を表示しています。
IDOR and broken object authorization testing playbook. Use when requests expose object identifiers, tenant boundaries, writable fields, or missing object-level authorization checks.
日本語の概要は準備中です。原文の説明を表示しています。
Entry P1 category router for file access and upload workflows. Use when testing download endpoints, file paths, local file inclusion, upload flows, preview pipelines, archive extraction, or storage and sharing boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or reviewing code that parses user input, builds SQL/shell commands, handles secrets/credentials, hashes passwords, changes auth checks, deserializes untrusted data, or constructs paths/URLs from input
日本語の概要は準備中です。原文の説明を表示しています。
Client-side routing with data APIs — loaders, actions, error boundaries, search params, nested layouts, and code splitting
日本語の概要は準備中です。原文の説明を表示しています。
Qwik resumable framework - zero hydration, $ lazy boundaries, signals, Qwik City file-based routing, routeLoader$, routeAction$, server$ RPC, serialization rules
日本語の概要は準備中です。原文の説明を表示しています。
File-based routing, loaders, actions, defer streaming, useFetcher, error boundaries, progressive enhancement
日本語の概要は準備中です。原文の説明を表示しています。
Error boundary patterns, fallback UI, reset/retry, react-error-boundary library, React 19 createRoot error hooks
日本語の概要は準備中です。原文の説明を表示しています。
Frontend specification planning frameworks. Use when a spec touches UI components, forms, client state, or user-facing flows. Covers UI-state completeness (loading, error, empty, success), component boundaries, form validation contracts, state ownership, and measurable UI success criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Pino logging, Sentry error tracking, Axiom - structured logging with correlation IDs, error boundaries, performance monitoring, alerting
日本語の概要は準備中です。原文の説明を表示しています。
Audit essays, reports, literature reviews, dissertations, proposals, and source-backed assignments for high-score academic quality. Use when the user asks whether a paper can get a high grade, wants teacher/rubric feedback addressed, needs a pre-submission review, or needs checks for strict rubric compliance, academic standards, prompt/rubric alignment, argument quality, comparative analysis, evidence hierarchy, table/figure integration, citation specificity, conclusion strength, academic language, source-claim integrity, or evidence boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Configure, implement, and test Pulp's optional desktop Ableton Link tempo-sync adapter while preserving the developer-supplied SDK, licensing, realtime, latency-compensation, and no-install boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or reviewing Vue 3 + TypeScript project structure, SFC/component boundaries, composables organization, route composition, Pinia ownership, API/error/styling defaults, directives, or repository-wide Vue conventions. Prefer narrower skills for forms, data fetching, tests, accessibility, virtualization, animation, or security deep dives; Chinese triggers include Vue 3 project specification, Vue component architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or reviewing Next.js 14+ App Router projects, file routes, layouts, server/client component boundaries, SSR/SSG/ISR, streaming, metadata, middleware, server actions, or Next-specific data fetching. For generic client React component architecture, apply the project's React conventions separately; Chinese triggers include Next.js, App Router.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or reviewing React + TypeScript project structure, feature/module boundaries, component architecture, hooks organization, routing composition, state/API/error/styling defaults, or repository-wide React conventions. Prefer narrower skills for forms, data fetching, tests, accessibility, virtualization, animation, or security deep dives; Chinese triggers include React project specification, React component architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on record, collection, value, responsibility, delegation, or algorithm boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on function structure, naming, parameters, shared context, or phase boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。