> Brief statutes and legislative Acts using the MAPS + RULES framework. Use when briefing statutes, analyzing legislative text, mapping statutory structure, extracting rule-modules from provisions, applying statutes to scenarios, or any statutory analysis task. Triggers include "brief this statute," "analyze this Act," "map the statute," "apply [statute] to [scenario]," "what are the elements of [provision]," "statutory analysis," or references to codified sections (such as 42 U.S.C. sections or Texas Health & Safety Code). Supports two modes - (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies statutory provisions to specific facts.
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill statute-briefer
Produce structured statute/Act briefs that (a) map the architecture of the entire statute/Act and (b) express operative provisions as rule-modules. Optionally apply provisions to scenarios with verbatim quotations.
Mode A: Text-only briefing
Mode B: Scenario-driven briefing
If citation/version missing, label brief as "text-as-provided" without recency claims.
Every brief produces two layers. In Mode B, prepend the Scenario Module.
See references/scenario-template.md for detailed template.
Six components:
Five components:
For each major operative provision (or scenario-relevant provisions), produce a rule-module.
See references/rule-module-template.md for detailed template.
Rule-Module required fields:
Mode A (no scenario): Major operative provisions = primary prohibitions/requirements/entitlements + enforcement/remedies + key definitions + preemption/savings/severability/venue
Mode B (with scenario): Prioritize provisions governing scenario issues + conditioning definitions/enforcement/exceptions. Still include full structure map.
| Constraint | Structure Map | Rule-Modules | Definitions |
|------------|---------------|--------------|-------------|
| Short | Spine outline only | Most relevant only | Key scope terms only |
| Standard | Major divisions complete | Core operative provisions | Terms affecting scope |
| Long | Full detail | All operative provisions | Comprehensive index |
Scenario Module
Scenario synopsis
Issues framed as statutory questions
Relevant excerpts (verbatim)
Application map (statute-to-facts)
Context map (where excerpts live)
Not used but structurally important
MAPS
Citation and text status
Purpose
Structure map (entire Act)
Scope and coverage
Definitions and interpretive rules
RULES
Rule-Module: [Provision cite]
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take lawve-ai/statute-briefer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.