「document」の検索結果

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

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

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

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

Generate KiCad schematics from a Circuit Weaver design.yaml or a project's own checked-in generator. Use for large, repetitive, or machine-synchronized designs. Prefer the Circuit Weaver CLI unless the project actually contains and documents its own generation scripts.

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

Build a timeframe-bounded research dossier by decomposing a topic into year orchestrators and month-level research passes that each write one condensed paragraph plus sources directly into a target file. Use when the user asks for a dossier, timeline, chronology, release history, or month-by-month research bounded by specific years or months. Not for timeless explainers or single-document summaries with no temporal scope.

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

Fix data that has gone wrong and change shape without breaking what reads it: duplicates, nulls, inconsistent document shapes, a field that means two things, a column that has to change. Use when a report cannot be built because the data is not in the right shape, when duplicates, nulls or inconsistent shapes are producing wrong numbers, when a field is needed or has to change, before a migration, or when onboarding data from a new source that does not match the standard shape.

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

Convert any pile of documents (PDF, Word, HTML pages, wiki exports, PowerPoint slides) into clean, LLM-ready markdown context: inventories the sources, picks the right extractor per file type (pdftotext or PyMuPDF for PDF, pandoc or mammoth for docx, readability extraction for HTML.

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

Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.

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

Audit a pharmaceutical regulatory submission system -- evaluate eCTD backbone assembly and XML validation, CTD module completeness (Modules 1-5), FDA ESG and EMA CESP gateway integration, document authoring and publishing workflows, ICH M4/M8/E3 guideline compliance.

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

Analyze mental health clinic and therapy practice software including appointment scheduling optimization with no-show backfill, therapist-client matching algorithms (specialization, modality, caseload balance), session documentation workflows (SOAP, DAP, BIRP templates).

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

Map a cloud system against NIST SP 800-53 Rev. 5 + FedRAMP baselines to produce the documentation an authorization needs — System Security Plan (SSP), Control Implementation Summary (CIS), Plan of Action and Milestones (POA&M), Continuous Monitoring (ConMon) Plan..

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

Audit legal aid and public defense case management systems -- client intake workflows, Federal Poverty Level eligibility screening accuracy, conflict-of-interest checking, document assembly and e-filing integration, court deadline calculation with rule-based calendaring.

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

Analyze game design documents and implementations for core gameplay loop clarity and depth, XP leveling curves and unlock pacing, difficulty curve spikes and plateaus, skill tree viability, player motivation via Self-Determination Theory.

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

Score your codebase 0-100 across complexity, coupling, cohesion, test coverage, documentation, churn hotspots, dependency health, and lint/type safety. Triggers: 'how healthy is this codebase', 'check code quality', 'score my project', 'find tech debt hotspots'.

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

Rewrites existing landing pages, blog posts, and documentation so AI search engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini) cite them. Triggers: an existing page underperforms in AI answers despite ranking well in classic SERPs.

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

Analyzes audit readiness systems for internal control testing, evidence collection workflows, statistical sampling methodology, audit finding documentation, and remediation tracking using PCAOB, ISA, and SOX compliance frameworks..

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

Analyze caregiver coordination platforms for scheduling optimization, task assignment, handoff communication, family/professional caregiver integration, care plan compliance, burnout prevention, and documentation workflows..

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

Analyze government benefits processing software for eligibility determination, application workflow efficiency, document verification, error rates, appeal tracking, multi-program coordination, and ADA/Section 508 compliance..

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

Best practices for building and maintaining applications with PowerSync: Cloud and self-hosted setup, sync configuration, client SDK usage, backend integration (Supabase, custom Postgres, MongoDB, Azure DocumentDB, MySQL, MSSQL), schema changes, watch and reactive queries (useQuery), attachments, the upload queue, and debugging. Use this skill whenever the user mentions PowerSync, a @powersync/* package (@powersync/web, @powersync/react-native, @powersync/node), the powersync Flutter/Dart package, the powersync Rust crate, wa-sqlite, offline-first sync, local-first architecture, sync rules, sync streams, uploadData, fetchCredentials, disconnectAndClear, logout or user switching in a synced app, real-time data replication, Electric Cloud migration, Electric Shapes, an app stuck on Syncing, data not syncing, or wants to add offline-capable sync to a mobile or web app, even if they do not explicitly name PowerSync.

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

Write a compelling sales proposal. Use when the user says "write a sales proposal", "put together a proposal", "draft a proposal for this prospect", "create a business case", "write up our recommendation", "how to structure a proposal", "proposal template", "executive summary for a deal", or wants to create a written document that moves a prospect toward a decision.

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

Update user personas from new feedback, pilot data, or research. Use this skill when: - New pilot data or feedback reveals changed user behaviors or pain points - Annual persona review is due (1-2x per year) - New user segments are discovered that need persona documentation - Existing personas need validation against recent data

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

Manage QA release gates - go/no-go decisions, release sign-off reports, defect triage, and release readiness communication. Use this skill whenever a QA lead or manager needs to formally assess whether a build is ready to ship. Trigger on phrases like "release sign-off", "go or no-go", "is this ready to release", "defect triage", "release gate", "approve the release", "block the release", "release readiness", "quality gate", "sign off on this build", "triage these bugs", or any request to make or document a formal release decision. Also trigger when a release manager or PM asks "what's the QA status?" or "can we ship this?".

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

Audit feature specs against India's Digital Personal Data Protection (DPDP) Act. Use this skill when: - Writing or reviewing any feature that handles user data (especially children's data) - Auditing a spec's Personal Information section for completeness - Checking a feature against DPDP Act 2023 requirements - Preparing compliance documentation before engineering review - Verifying masking, retention, and consent policies are defined for all PII

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

Design and write QA test artifacts - test cases, test plans, acceptance criteria, API test specs, and PR testability reviews. Use this skill whenever a QA engineer or SDET needs to translate requirements, user stories, or feature specs into structured test documentation. Trigger on phrases like "write test cases", "create a test plan", "define acceptance criteria", "review this PR for testability", "write API test specs", "test coverage for this feature", "what should we test", "how do we test this", or any request to structure what and how to test before execution begins. Also trigger when a developer asks "is this testable?" or a PM asks "what are the edge cases?".

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

Design and document a marketing growth experiment. Use when the user says "run a growth experiment", "test this channel", "growth test", "I want to experiment with [channel]", "traction experiment", "acquisition experiment", "let's test if [channel] works for us", "bullseye framework", "which channels should we try", "run a traction test", or wants to systematically test a marketing or acquisition channel before committing budget. For page-level conversion hypotheses, see page-cro. For copy variants to test, see ab-copy-writer. For recording the result, see retro.

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