1,584 件 ・ 関連度順
概要と使いどころ
Legal document generation and compliance guidance for indie Apple developers. Covers privacy policies, terms of service, EULAs, GDPR/CCPA/DPDP compliance, and Apple App Store legal requirements. Use when user needs legal documents or compliance guidance.
日本語の概要は準備中です。原文の説明を表示しています。
omicsViewer visualizes ExpressionSet (or SummarizedExperiment) in an interactive way. The omicsViewer has a separate back- and front-end. In the back-end, users need to prepare an ExpressionSet that contains all the necessary information for the downstream data interpretation. Some extra requirements on the headers of phenotype data or feature data are imposed so that the provided information can be clearly recognized by the front-end, at the same time, keep a minimum modification on the existin
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Peering Service development including limits & quotas. Use when validating prefix size, routing setup, BGP config, RPKI status, or AS number requirements, and other Azure Peering Service related development tasks. Not for Azure Internet Peering (use azure-internet-peering), Azure ExpressRoute (use azure-expressroute), Azure Virtual Network (use azure-virtual-network), Azure Virtual WAN (use azure-virtual-wan).
日本語の概要は準備中です。原文の説明を表示しています。
Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions.
日本語の概要は準備中です。原文の説明を表示しています。
Category and brand ungating — requirements, documentation, appeal process, restricted categories guide
日本語の概要は準備中です。原文の説明を表示しています。
Build a product-specific Amazon FBA prep, labeling, packing, and shipment-readiness plan. Use when a seller asks how to prepare units for FBA, choose barcode and labeling steps, plan poly-bagging, bubble wrap, sets, case packs, cartons, dangerous-goods review, supplier or prep-center instructions, or prevent receiving delays. Do not use as a substitute for current Seller Central requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Product compliance and safety — certifications, labeling requirements, restricted substances, documentation
日本語の概要は準備中です。原文の説明を表示しています。
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
日本語の概要は準備中です。原文の説明を表示しています。
Create a packaging design brief — structure, visual direction, hierarchy, materials, and unboxing experience. Use when the user says "packaging design", "packaging brief", "product packaging", "packaging direction", "label design", "packaging identity", "unboxing experience", "packaging look and feel", "brief my packaging designer", "packaging for my product", "packaging strategy", "retail packaging", "e-commerce packaging", "what should my packaging look like", or is briefing a designer, agency, or manufacturer on packaging requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Review uncommitted code changes to find unreasonable design, unfinished requirements, potential bugs, missed reuse opportunities, and optimization opportunities. Use when the user asks for a review of pending, uncommitted, or unpublished code changes and expects both findings and concrete improvements.
日本語の概要は準備中です。原文の説明を表示しています。
25 real-world system design case studies condensed from Alex Xu's System Design Interview Vol 1 and 2 - requirements, architecture, deep dive insights, key takeaways
日本語の概要は準備中です。原文の説明を表示しています。
Source reputation tiers, cross-referencing methodology, bias detection, and citation format requirements
日本語の概要は準備中です。原文の説明を表示しています。
Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
日本語の概要は準備中です。原文の説明を表示しています。
Requirements quality critique dimensions for peer review - confirmation bias detection, completeness validation, clarity checks, testability assessment, and priority validation
日本語の概要は準備中です。原文の説明を表示しています。
Toyota 5 Whys methodology with multi-causal branching, evidence requirements, and validation techniques
日本語の概要は準備中です。原文の説明を表示しています。
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
日本語の概要は準備中です。原文の説明を表示しています。
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a NEW landing page, sales page, or single-product page has to be built — seven-section structure, one page one goal one CTA, copy per block, mobile-first rules, technical and speed requirements, tracking plan, A/B test plan, and a dropshipping single-product mode. Trigger on 'landing page brief', 'build a sales page', 'I need a landing page', 'brief for the dev', 'Shopify product page', 'what should go on the page'. Also use when ad traffic is ready and there is nowhere to send it. Not for — the ad copy pointing at the page, see `05-ad-copy-global`; the offer and its value stack, see `31-offer-design-global`; scoring a finished design, see `47-design-review-global`; coded email, see `49-html-email-template-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks how big the project is, what has shipped, or for project statistics. Reports phase progress, plan execution, requirements completion, git history metrics, and timeline through the GSD workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Use when every phase in a milestone is complete and the user wants to archive it, tag the release, and start the next version. Archives roadmap and requirements to .planning/milestones/, updates PROJECT.md, then tags the version.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the current milestone has shipped and it is time to scope the next one, or when the user asks to start a new milestone. Updates PROJECT.md, then runs questioning, research, requirements, and roadmap.
日本語の概要は準備中です。原文の説明を表示しています。
Use when onboarding someone to a finished milestone or preparing a team review. Reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION artifacts into one MILESTONE_SUMMARY in .planning/reports/, then offers Q&A.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to think through an idea before committing to a plan, e.g. /gsd-explore auth strategy. Runs a Socratic session, optionally spawns research, then routes output to notes, seeds, requirements, or new phases.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task, before touching code
日本語の概要は準備中です。原文の説明を表示しています。