「requirements」の検索結果

Generates performance-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Performance Optimization pillar of the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify performance requirements, and provide actionable recommendations for resource allocation, modular design, and elasticity.

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

Generates reliability-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework. Use this skill to evaluate a workload, identify reliability requirements, and provide actionable recommendations for build, deploy, and manage the workload reliably in Google Cloud.

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

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

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

Generates cost optimization guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify cost requirements and constraints, and provide actionable recommendations for build, deploy, and manage the workload cost-efficiently in Google Cloud.

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

QA a change by driving the running dev app like a real QA engineer - start the server and a real browser session, write a checklist from the agreed requirements and the diff, execute every item with evidence, then go looking for anything that looks off even where the diff did not touch. Reports findings by severity and separates regressions from pre-existing problems. Use after a change is implemented and the gates pass, when the user asks to "QA this", "test it in the app", or "check it actually works".

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

Implement a change end-to-end from a freeform prompt - settle the requirements, design the engineering approach and get it approved, implement with TDD, run the format/compile/credo/coveralls gates without shortcuts, self-review the diff like a senior engineer, QA the finished change in the running app, record a demo video when it is visible there, then commit and open the PR. Use when the user wants to "complete an issue", "work the ticket", or hands over a description of something to build.

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

GitHub Pull Request creation specialist. Analyzes user requirements to create PRs with structured titles and bodies matching the user's query language. Handles git change analysis, PR draft creation, user confirmation, and final PR creation via gh CLI.

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

Research current job markets and hiring requirements, analyze recent job descriptions (JDs), compare them with a user's resume, projects, skills, and constraints, and turn evidence gaps into prioritized career actions. Use when students, job seekers, or career changers ask about current role or industry outlook (including “现在行情怎么样”), whether a role or JD fits them (including “这个JD适合我吗”), cross-platform JD sampling, resume evidence gaps or truthful tailoring, what career skill to learn next, target-role course or certificate decisions, application readiness, or a capacity-bounded 30/60/90-day job-search plan. Do not use for unrelated personal or education advice, simple factual lookups, automatic job applications, or unsupported resume rewriting.

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

Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore the code, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.

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

Comprehensive AI safety and alignment audit framework for businesses deploying AI agents. Built around the UK AI Security Institute Alignment Project standards (2026), EU AI Act requirements, and N...

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

Adversarial implementation review based on Block's g3 dialectical autocoding research. Use when validating implementation completeness against requirements with fresh objectivity.

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

You are an academic writing expert specializing in scholarly papers, literature reviews, research methodology, and thesis writing. You must adhere to strict academic standards in all outputs.## Core Requirements1. **Output Format**: Use Markdown exclusively for all writing outputs and always wrap the main content of your response within <ama-doc></ama-doc> tags to clearly distinguish the core i...

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

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

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

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.

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

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

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

Bridge the gap from product specifications to implemented features. Document requirements, acceptance criteria, tech design, and track implementation progress in Notion.

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

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

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

OWASP ASVS v5.0 security verification skill with Drupal 11 mappings. Use when performing security code reviews, implementing security requirements, or verifying security compliance in Drupal projects.

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

Test-Driven Development workflow for Software Metrics Machine. Covers test frameworks (Vitest 4.x for CLI/REST/core/utils, Jest 30.x for webapp), test patterns (describe/it, builder pattern, mocks via vi.fn), test commands, coverage requirements, and the Red-Green-Refactor cycle. USE FOR: write tests, run tests, test this, add tests, testing, coverage, TDD, test-driven development, vitest, jest, test pattern, test convention. DO NOT USE FOR: linting (use lint skill), building (use build commands directly), debugging production issues.

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

Turns an existing Product Requirements Prompt at .ai/[feature]/prp.md into a step-by-step task list of parent tasks and sub-tasks, saved to .ai/[feature]/tasks.md and committed. Use when a PRP is ready to be broken down into implementable work, or when planning how a feature will be built before any implementation starts. To write the PRP itself first, use prp- generation.

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

Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.

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

Generate Product Requirements Document from feature intent/description

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

Iteratively define problem and solution shapes.

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

Used by the Lead agent during Phase 6 (Brainstorm) to collaboratively explore user intent, requirements, and alternative approaches before locking in the architecture. Helps turn raw ideas into fully formed specs through natural dialogue.

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