Use when drafting California court documents for a self-represented (pro se / "In Pro Per") litigant. Triggers include "pro se", "in pro per", "self-represented", "representing myself", "pro-se drafting framework", "draft without an attorney", "pro se California", "Judicial Council forms", "fee waiver", "FW-001", "how do I serve", "CCP 415", "CCP 1013", "Self-Help Center", "In Pro Per", or when the user describes themselves as the plaintiff or defendant directly. Covers the Parker drafting framework adapted for California, "In Pro Per" vs. "self-represented litigant" terminology, service protocols under CCP §§ 412.10-417.40 and 1010-1020, Judicial Council form use, In Forma Pauperis fee waivers (FW-001 / FW-003), and California- specific pro se resources. Layer on top of ca-statewide-format and the applicable county skill (ca-lasc, ca-sfsc, or ca-county-courts).
How to install ca-pro-se?
codearranger/claude-legal/ca-pro-se
$npx -y skills add codearranger/claude-legal --skill ca-pro-seInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/codearranger/claude-legal" --skill "codearranger/claude-legal/ca-pro-se"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/codearranger/claude-legal" that are relevant to the current task. Run `npx skills add "https://github.com/codearranger/claude-legal"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- gpt-image-2Create or edit images with Pilio GPT Image 2 through the unified Pilio developer API.Jul 2026
- spec-driven-implementationDrive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs…Jul 2026
- review-prReview a pull request diff and write structured feedback to review.json for the workflow to publish.Jul 2026
- write-product-specWrite a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation.Jul 2026
- write-tech-specWrite a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints.Jul 2026
- fix-errorsFix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests.Jul 2026
