Results for “rules”

Use when task matches design-usability-rules design guidance for IA, usability, responsiveness, systems, motion, and visual QA.

Converts legacy agent resources such as subagents, commands, and rules into the unified Agent Skills format, with classification, conversion, and verification steps.

Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.

Defines the LEND.AI assistant persona: identity, tone, and interaction rules for a Spanish-speaking senior mentor that teaches while working, questions decisions, and requires confirmation before acting.

Bootstraps the always-loaded rules layer for a new repository: writes a CLAUDE.md skeleton and a workflow.md model-notes rule, and optionally installs a native git pre-commit hook. Skips repos already rendered by the Loam Copier template.

Generates a structured post-task reflection capturing surprises, patterns, prompt improvements, and gotchas, writing it to a markdown file without modifying project rules.

Use only when the request concerns standards, responsibility, complexity, smells, naming, refactoring catalogs, or task-plan rules; not routine work.

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

Detect business email compromise (BEC) attacks using email gateway rules, behavioral analytics, and financial process controls.

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.

Comprehensive architecture baseline scan. Two-wave AI analysis producing blueprint.json, per-folder CLAUDE.md, AI-synthesized rules, and health metrics. Use for first-time baselines or major refactors.

Optimizes agent context setup by structuring rules, specs, source files, error output, and conversation history to improve output quality.

Guides users through selecting and installing skills and rules from the Everything Claude Code project, verifying paths and optionally optimizing installed files.

Loads and manages company context for C-suite advisor sessions, detecting stale context, enriching it during conversations, and enforcing privacy rules before external API calls.

Hunt for adversary persistence via Windows Scheduled Tasks by analyzing task creation events, suspicious task actions, and unusual scheduling patterns.

Draft privacy policies, terms of service, disclaimers, and legal notices with GDPR, CCPA, and other regulatory compliance.

Design and optimize revenue operations, including lead lifecycle rules, scoring, routing, handoffs, and CRM process automation for marketing, sales, and customer success alignment.

Drafts structured goal-loop prompts for long-running agent work with verifiable stop conditions, validation commands, and documentation requirements.

Turns a one-sentence game concept into a complete, playable design with rules, components, and variations, and also designs gamification systems for real-world goals.

Audits AGENTS.md and CLAUDE.md files for bloat, redundancy, and ineffective rules, then runs A/B evals to prove which instructions are dead weight.

Use when designing a course, assessment, or student-feedback workflow and deciding where AI assistance is acceptable, when grading or feedback must stay within academic-integrity and FERPA/KVKK boundaries, or when AI-use rules for students need stating.

Turns a local folder into a searchable, maintainable knowledge base for AI agents, handling setup, navigation, content ingestion, querying, and health checks without external databases or RAG systems.

Automatically organizes files in a directory into a clean structure based on configurable rules — by file type, date, project, or priority — with support for duplicate detection, naming conventions, and archival strategies. Use when the user requests file organization or provides relevant inputs for this workflow.

Reconcile this session's code delta back into the Living Blueprint and per-folder intent layer so they stay an accurate snapshot of the codebase. Mostly descriptive (what the code now is), not rules. Pure producer — edits files only, never commits or opens a PR.

Defines an inter-agent communication protocol for C-suite agent teams, including invocation syntax, loop prevention, isolation rules, and response formats to coordinate cross-functional analysis and board meetings.

Converts technical books and documents (PDF, EPUB, DOCX, HTML, Markdown, RTF, MOBI) into structured agent skills with frameworks, mental models, chapter references, and decision rules. Includes a full extraction pipeline for turning owned documents into reusable skills.

Generate implementation plans from approved designs — plan-generator, phase-based plans, parallel batch execution, task dependency graph, owner skill routing, acceptance criteria, global done criteria, plan frontmatter, layout contract, interaction contract, anti-drift rules, plan format, AD-2 byte-for-byte gate, scope definition, execution plan, phases and batches, task anatomy, plan file format

PROACTIVE SKILL — automatically apply whenever writing, generating, or editing any text that is mainly in Chinese. No user trigger needed. Also use when the user explicitly asks to "fix Chinese", "修改中文", "去翻译腔", "去AI味", "fix Chinese formatting", or "review Chinese text". Eliminates AI-sounding expressions and translation artifacts. Enforces Chinese-English mixed formatting rules (spacing, punctuation, bold formatting).

Creates or updates a repo's CLAUDE.md by exploring the code and adding the standard workflow sections (git/PR rules, changes that require human review, non-obvious context). Use whenever the user is starting in a new repo, says "set up the CLAUDE.md", "onboard this repo", "there's no CLAUDE.md here", or asks to complete or improve an existing CLAUDE.md — or in Spanish "armá el CLAUDE.md", "iniciá este repo", "falta el CLAUDE.md acá". Also run it before the first time `plan` runs in a repo that has no CLAUDE.md yet.