1,256 件 ・ 関連度順
概要と使いどころ
Audit the project's documentation (CLAUDE.md, .claude/rules, skills, README, CONTRIBUTING, SECURITY, .env.example, app/data/*.md, learn articles) against the actual code and config, and fix drift. Use after refactors, dependency or workflow changes, or on a schedule.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when explaining a technical concept and adapting depth, pacing, and examples to the learner's readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a learner needs a structured review session prioritizing high-value topics by recency, error history, and upcoming deadlines.
日本語の概要は準備中です。原文の説明を表示しています。
Author an editorial HTML+SVG diagram with the Diagram Design kit - choose the visual type, read its reference, start from an example, and satisfy the safety and accessibility contract that diagram_write({kind:"html"}) enforces.
日本語の概要は準備中です。原文の説明を表示しています。
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
日本語の概要は準備中です。原文の説明を表示しています。
Refine an existing skill in place with minimal diffs. Trigger when asked to improve a skill's trigger description/frontmatter, workflow text, metadata, scripts/references/assets; also for requests to iterate, refactor, rename, or fix a skill using usage/session-mining evidence (for example from /tw-seq).
日本語の概要は準備中です。原文の説明を表示しています。
Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another workflow (for example /tw-fix) with invariant checks first.
日本語の概要は準備中です。原文の説明を表示しています。
Given an existing Style, generate a human-readable brand guidelines document covering colors, typography, voice, do/don't, imagery rules, and usage examples. Use when the user asks for a brand book, brand guide, or design system document.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base synthesized from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14 by the BKCASE Project. Use for the established systems-engineering canon: SE fundamentals and foundations (systems science, systems thinking, the systems approach, modelling/MBSE), the life cycle (ISO/IEC/IEEE 15288/24748/24774 process, development & agile approaches, model selection/tailoring), technical management, concept definition, architecture/realization (the Vee), V&V, maintenance/sustainment, SE standards, and the application contexts (product, service, enterprise, systems-of-systems, healthcare), plus enabling SE (business/team/individual), related disciplines, quality attributes/specialty engineering, implementation examples, and emerging knowledge. Good for grounding background, vocabulary, and prior-art positions across all eight SEBoK Parts. SCOPE LIMITS: this pack is SEBoK v2.14 only (released 2026-05-18); it synthesizes and signposts rather than reproducing the source — it does not reproduce ISO/IEC/IEEE standard text, is a curated guide (not a complete textbook), and is thin on AI-integration depth (Part 8 is a staging area, not settled practice). LICENCE: content is CC BY-NC-SA 3.0 — non-commercial use only, attribution to the BKCASE Project required, share-alike obligations carry forward.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NIST Framework for Cyber-Physical Systems (SP 1500-201/202/203, v1.0, 2017). Use for engineering and analyzing cyber-physical systems (CPS) and IoT: the CPS Framework's aspect × facet grid (nine aspects of concern examined through conceptualization, realization, and assurance facets), cross-property trustworthiness risk management (safety/security/privacy/reliability/resilience together), data interoperability (syntactical/semantic/contextual, canonical models, identifiers, provenance), the timing aspect (time-interval classes, time domains, time-aware networking) and secure/resilient time (GNSS jamming/spoofing, PTP/NTP attacks, holdover, the clock-error model and Allan/MTIE metrics), plus the use-case requirements method. Bridges IT and OT under a clock. Scope limits: a 2017 living/draft document, thin on post-2017 standards and on detailed control catalogs; it names but does not reproduce ISO/IEC/IEEE 42010 and 15288 process text or permission-licensed third-party figures.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems — the avionics/medical slant — via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Cost Estimating Handbook (CEH) v4.0. Use for NASA's 12-step, three-part cost estimating process (Project Definition, Cost Methodology, Cost Estimate); the WBS, CADRe, and ONCE data backbone; estimating methodologies (analogy, parametric/CER, engineering build-up, EVM, Delphi); ground rules and assumptions, data normalization and inflation (BY/CY/RY); the point-estimate-to-S-curve cost-risk chain and Unallocated Future Expense (UFE) reserves; Joint Cost and Schedule Confidence Level (JCL) analysis via probabilistic cost-loaded schedules; decision-support analyses (sensitivity, trade studies, make/lease-vs-buy, affordability, CAIV); and economic analysis (discounting, NPV, OMB Circular A-94). The cost-estimating complement to NASA's SE and risk packs. Does NOT reproduce the handbook's tool-specific procedures, worked examples, or appendix-depth methods (it names the appendices), nor cover full DoD/GAO cost guides, schedule construction, or formal risk management beyond the cost interface.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Fault Management Handbook (NASA-HDBK-1002, Draft 2, April 2012). Use for the systems-engineering discipline of designing what a system does when it fails — the fault/failure/anomaly vocabulary, the five FM strategies (two prevention strategies — design-time fault avoidance and operational failure avoidance — plus three tolerance strategies — failure masking, failure recovery, and goal change), the six FM process activities across NASA mission phases Pre-A to E, response-latency-versus-time-to-criticality (TTC) design trades, fault/failure containment regions and FEPPs, the four redundancy approaches, top-down FM requirements development, FM verification vs. validation, the seven dedicated FM milestone reviews (FMCR/FMARR/FMPDR/FMCDR/FMTRR/FMLRR/FMCERR), FM organizational structure, and mined NASA Lessons Learned. Space-mission oriented (flight/ground/operations); spacecraft examples throughout. IMPORTANT: built from an UNAPPROVED DRAFT — several sections (detailed architecture building blocks, the Assessment & Analysis guidance, and Operations & Maintenance) are placeholders in the source and are thin here. Thin on detailed FDIR algorithms, terrestrial/IT fault management, and any approved-standard terminology that may have changed since Draft 2.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Probabilistic Risk Assessment Procedures Guide (NASA/SP-2011-3421, 2nd ed.). Use for quantitative PRA of aerospace and safety-critical systems: the risk triplet and scenario logic stack (MLD, ESD, event trees, fault trees, minimal cut sets), Bayesian data collection and parameter estimation, aleatory/epistemic uncertainty modeling and common-cause failure (Alpha Factor, beta-factor, CCBE), human reliability analysis (THERP, CREAM, NARA, SPAR-H), context-based software risk (CSRM), physics-based and structural/phenomenological models (stress-strength, limit states, FORM/SORM, NASGRO, range safety), uncertainty propagation and importance measures (F-V, RAW, Birnbaum, DIM), and launch-abort modeling with worked PRA examples. This is the QUANTITATIVE engine beneath NASA's risk doctrine — for the qualitative RIDM/CRM decision framework use the nasa-risk pack. Thin on programme management, organisational risk governance, and non-aerospace regulatory contexts; aerospace-focused and anchored to the 2011 second edition.
日本語の概要は準備中です。原文の説明を表示しています。
Local, private capture of medical data: diagnoses, symptom histories and examination plans. No BACH origin — custom design with its own SQLite store. Strictly local, no cloud transfer.
日本語の概要は準備中です。原文の説明を表示しています。
Prüfungsvorbereitung, Selbsttests, Probeklausuren und systematische Fehleranalyse.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a control list and an audit scope into draft evidence requests grouped by control owner, each with the control as stated, the audit period, evidence examples (commonly requested) and a proposed due date derived from the fieldwork dates. Never judges whether evidence is sufficient, never selects the sample and never sends a request; the auditor decides. Use when the user asks to "prepare the evidence requests", "draft the PBC list", "build the evidence request pack for the audit" or "what do we need to ask each control owner for". Do not use for document requests and interview questions built from an audit plan, use audit-prep-pack instead; to check claims in a report against sources, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Answers an employee's or manager's HR policy question strictly from the policy documents the user supplies or the agent can reach as knowledge: a DRAFT answer that quotes the governing clause with its document, version and clause reference, lists the conditions and exceptions the text states, returns UNKNOWN where the documents are silent and names the role to ask. Never invents a rule, fills a gap from general practice or decides an individual's case. Use when the user asks to check a policy, for example "what does the policy say about", "am I entitled to", "how many days of leave do I get", "what is the process for requesting", "does the handbook allow" or "which clause covers". Do not use for comparing two policy versions or briefing a change, use policy-change-briefing instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a DRAFT weighted supplier evaluation matrix from supplier responses and the panel's agreed criteria, weights and scale: a provisional score per cell with the quoted evidence and anchor behind it, a register of every missing or partial answer, and calibration and sensitivity flags. Provisional for panel moderation; never recommends, awards or disqualifies. Use when the user asks to score, weight or rank supplier, bid or tender responses against agreed criteria, for example "score these bids", "build the evaluation matrix", "weight the tender responses" or "rank the suppliers against our criteria". Do not use for a side-by-side comparison without scores, use rfp-comparison-pack instead; for writing the criteria, use rfp-requirements-pack instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a DRAFT self-assessment, peer feedback note or manager review narrative from the evidence the writer supplies (goals, examples, metrics, notes), in the review template where given: every sentence tied to a numbered evidence item, unsupported claims removed and logged, and a gaps list to complete before submitting. Never assigns, suggests or implies a rating, score, ranking, pay or promotion outcome. Use when the user asks to "write my self-assessment", "draft peer feedback for a colleague", "turn these notes into a performance review", "help me write the year-end review for my report", "summarise my achievements against my goals" or "draft the mid-year review". Do not use for a job description or role profile, use job-description-drafter instead; for a new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
A minimal example skill. Greets the user and demonstrates the SKILL.md format.
日本語の概要は準備中です。原文の説明を表示しています。
Use when locating TBQ3 documentation, function references, examples, or source docs under docs without loading the full corpus; supports rg-based search and curated topic/function indexes.
日本語の概要は準備中です。原文の説明を表示しています。