Results for “scope”

Trigger: writing style, copy editing, simple copy, prose check, text clarity. Scope: Writing clear, direct, and concise English copy. Boundary: Excludes code formatting or marketing value propositions.

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Runs and writes tests, verifies behavior, and orchestrates two-pass TDD across scoped modes, blocking on quality gates and never editing production code.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

Explains MariaDB-specific SET syntax and behavior, including scope rules, the SET STATEMENT ... FOR extension, and persistence differences from MySQL.

XSLT injection testing: processor fingerprinting, XXE and document() SSRF, EXSLT write primitives, PHP/Java/.NET extension RCE surfaces. Use when user-controlled XSLT/stylesheet input or transform endpoints are in scope.

Trigger: a11y, accessibility, ARIA, screen reader, contrast, keyboard, tap targets, focus. Scope: Audit web interface accessibility compliance (WCAG AA). Boundary: Do not use for general backend logic or CSS styling aesthetics.

Trigger: responsive layout, media queries, mobile view, desktop layout, tablet break points, thumb zone. Scope: Multi-device layouts, breakpoints, mobile touch zones. Boundary: Excludes backend API design or database scaling.

Trigger: web performance, slow load, bundle size, lazy loading, LCP, CWV optimization, fetch priority. Scope: Frontend optimization, loading speeds, asset minimization. Boundary: Excludes backend database indexing or visual design systems.

Trigger: marketing copy, landing text, CTA labels, value proposition, copywriting copy, conversion copy. Scope: Persuasive copy generation, conversion-focused taglines. Boundary: Excludes technical specifications or backend engineering.

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

Creates temporary encrypted one-time handoffs between autonomous agents, supporting mission briefs, scoped secrets, artifacts, and receipts via CLI or API.

Code review skill — auto-scopes from git changes, reads DOJO.md for project conventions, and produces structured findings with priority levels. Supports quick single-pass review and deep 3-agent parallel audit.

Design and author reusable subagents for specialized AI tasks. Use when the task needs an isolated agent persona, scoped system prompt, or reusable domain-specific assistant rather than a general skill.

Trigger: TDD, test first, unit testing, integration tests, mock assertions, test-driven dev. Scope: Writing test assertions before coding features, testing paradigms. Boundary: Excludes UX aesthetics or continuous deployment settings.

Record decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.

Guides through client library installation and authentication setup for the Data Manager API, including ADC configuration and required scopes.

Creates and maintains a minimal, high-signal AGENTS.md file for AI coding agents, covering package manager, file-scoped commands, commit attribution, and key conventions.

Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.

Create, name, scope, assign, and close GitHub milestones. Use when adding a milestone, deciding whether work belongs in one, or naming the next one. One axis per project (release / date / theme); never as labels.

Trigger: CRO, conversion optimization, checkout friction, user dropoff audit, funnel dropoff. Scope: Diagnosing and auditing checkout and landing page conversion bottlenecks. Boundary: Excludes direct code edits, styling modifications, or analytics database setup.

Trigger: empty list state, loader skeleton, error boundary layout, offline indicator, system fallback UI. Scope: UI fallback layouts, skeleton placeholders, client recovery views. Boundary: Excludes server-side API error status coding.

Trigger: form inputs, wizards, checkout forms, multistep forms, validation UI, input focus. Scope: User-friendly forms design, input constraints, progressive disclosure. Boundary: Excludes backend database schemas or server-side API validation.

Trigger: press release, PM memo, PRD memo, product launch narrative, launch story. Scope: Writing press releases and future launch stories for project alignment. Boundary: Excludes writing functional code or task tracking.

Use when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.

Review git diffs or file scopes for code reuse, quality, efficiency, and clarity issues, then optionally apply safe, behavior-preserving fixes.

Decomposes an approved specification into dependency-aware waves and atomic executable tasks with exact file scope, test-first actions, verification commands, and an execution gate.

Launches four parallel adversarial review agents covering security, scope, fidelity, and test gaps, then synthesizes findings into a ranked verdict for plans or feature branches.

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 downstream agents instead of click-driving the Datadog UI.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Guides SOC 2 Type II audit preparation with six forcing questions covering scope, control consistency, evidence tracking, and cross-walk to ISO 27001.

Convenes a council of specialized agents to debate important decisions, synthesizing independent perspectives into a structured recommendation and optional spec document.

Kotlin language fundamentals. Covers null safety, coroutines, flow, sealed classes, data classes, scope functions, and Kotlin 2.x features (K2 compiler, context parameters). Use for Kotlin/JVM, Kotlin/Native, Kotlin/JS work. USE WHEN: user mentions "Kotlin", "coroutines", "suspend", "Flow", "sealed class", "data class", "scope functions", "K2 compiler", "ksp", "Kotlin 2.x" DO NOT USE FOR: Kotlin Multiplatform setup - use `mobile/kotlin-multiplatform` DO NOT USE FOR: Compose UI - use `frontend-frameworks/compose-multiplatform` DO NOT USE FOR: Spring Boot Kotlin - use `spring-boot` framework skill

Identify, collect, and analyze ransomware attack artifacts to determine the variant, initial access vector, encryption scope, and recovery options.

Use Light DOM in LWC when third-party libraries or global CSS require document-level access, with guidance on scoped styles and managed-package constraints.

Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).