Results for “scope”

Markdown project memory for AI agents. Use for decisions, architecture, conventions, monorepo scopes, `.lore/`, or `lore` commands; not native `/init`/`/compact` or generic init/compress/audit/query.

Markdown project memory for AI agents. Use for decisions, architecture, conventions, monorepo scopes, `.lore/`, or `lore` commands; not native `/init`/`/compact` or generic init/compress/audit/query.

Runs a structured five-round brainstorm to capture actors, features, scope, constraints, and business rules before writing a spec.

Produce a decision-ready legal briefing — daily digest, topic research, or incident write-up — scoped to what a non-lawyer stakeholder needs to decide or act on.

Guide building a minimum viable product through manual-first, then processized, then productized stages. Use when someone is ready to build their first product or struggling with scope.

MoonPay PayBox payment vault for AI agents — official MCP at https://api.paybox.sh/mcp, OAuth 2.1, scoped credentials, and Cheshire mcp-server proxy tools (get_paybox_*).

Implement Python database access with parameterized SQL, transaction scope, connection helpers, and repository seams. Use when editing Postgres queries, repositories, transactions, pooling, or persistence boundaries in Python.

Trigger: security rules, credential leaks, auth tokens, input sanitization, threat model. Scope: Software security guidelines, threat prevention, secure data handling. Boundary: Excludes client-side web browser vulnerabilities.

Trigger: web security, XSS mitigation, secure cookies, CSRF, CSP headers, CORS policies. Scope: Frontend and browser-level security boundaries. Boundary: Excludes operating system file storage permissions.

Trigger: database schema, indexing, cache asidePattern, Redis caching, ORM models, Drizzle schema. Scope: Database query tuning, indexing, and data cache designs. Boundary: Excludes user identity validation.

Redesign Salesforce Flows to handle bulk data loads without hitting transaction limits, using collection-first patterns and safe transaction scope.

Creates Cursor rules in .cursor/rules/ with YAML frontmatter for persistent AI guidance, including scope and file pattern configuration.

Trigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.

Trigger: deployment pipeline, CI CD, Docker builds, DB migrations, expand contract database, Netlify. Scope: Application deployment, multi-stage builds, zero-downtime releases. Boundary: Excludes local editor settings.

Trigger: OAuth 2.1, JWT session, Secure cookies, Keychain storage, auth flow, user authentication. Scope: User authentication, session storage, authorization boundaries. Boundary: Excludes generic data caching.

Trigger: tech stack, preferred tools, SvelteKit, Bun, Drizzle, Zero Sync, Better Auth, Vite. Scope: Project tooling preferences, framework selections. Boundary: Excludes application logic or visual styling guidelines.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

Guides the creation of well-structured Claude Code skills and slash commands, covering skill types, scope, frontmatter settings, and file organization.

Entry P1 category router for reconnaissance and methodology. Use when mapping scope, discovering assets, fingerprinting technology, building endpoint inventory, and choosing the first high-value security testing path.

Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then productized. Use when someone is ready to build their first product or struggling with scope.

Query and filter Datadog logs from the shell using the Composio CLI. Run scoped log searches, pivot across services/environments, and export structured JSON for incident investigation and diagnostics.

Use with task-agent or review-agent for task-local cache scope, freshness, invalidation, and source-load risk. Do not use without a cache decision or as task owner.

Trigger: shopping cart, checkout conversion, checkout flow, payment trust, pricing layout. Scope: Commerce UX optimization, trust badges, checkout pathways. Boundary: Excludes payment gateway API integrations or backend authentication.

Trigger: design review, visual audit, layout inspection, QA checks, screenshot analysis. Scope: Performing design system compliance audits and interface QA. Boundary: Excludes functional unit testing or database indexing.

Trigger: REST API, GraphQL schemas, HTTP methods, RFC 7807, endpoint structure, API contracts. Scope: API schema design, error models, request/response structures. Boundary: Excludes client-side visual layouts.

Trigger: sitemap, navigation, menu structure, wayfinding, labeling, search facets, routing links. Scope: Visual hierarchies, wayfinding, navigation model, sitemaps. Boundary: Excludes backend route handlers or page performance tuning.

Composite skill — land a safe first PR in an unfamiliar repo without rediscovery loops or guessing at conventions. Chains onboard-new-repo (architecture + scripts + CI scan) → context-pack (relevant files + standards + ADRs for the scoped change) → scope-and-execute (narrow the task) → test-driven-development (write failing test first) → pr-to-release (open the PR). Use the first time you contribute to a repo OR when an unfamiliar contributor needs a guided first change.

Structures a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Share state between Blazor components across render mode boundaries using cascading values, scoped services with change events, or CascadingValueSource via DI.

Guides structured problem-solving through iterative reasoning steps, with support for revising conclusions, branching into alternative approaches, and dynamically adjusting scope as understanding evolves.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.

Identify, assess, and mitigate project risks across technical, scope, dependency, and timeline categories using a structured register and escalation rules.

Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then productized. Use when someone is ready to build their first product or struggling with scope.

Seven-role depersonalised panel review of framework artefacts (KUD, criterion bank, LT definition, crosswalk, scope-and-sequence) in sequential-isolation mode. Gate rule mean>=88 AND no role<70.

Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.

Trigger: standard work, deming first, feedback loop checks, decision rights, delegation check. Scope: Engineering operating models, team governance, task feedback loops. Boundary: Excludes direct code implementation or design templates.