Use when a California defendant has just been served with a summons and complaint. Triggers include "I was just served", "I got served with a summons", "how much time to respond", "deadline to answer a California complaint", "30 days to answer", "first steps after being sued", "should I file a demurrer", "motion to strike California", "anti-SLAPP motion", "affirmative defenses", "cross-complaint", "default California". Covers the from-service-through-response window: CCP § 412.20(a)(3) 30-day response (plus 10 days for mail); response options (Answer, Demurrer under § 430.10, Motion to Strike under § 435, Anti-SLAPP under § 425.16, Motion to Quash under § 418.10, Cross-Complaint under §§ 426.10–426.50); mandatory meet-and-confer; affirmative defenses; default procedures under § 585.
How to install ca-first-30-days?
codearranger/claude-legal/ca-first-30-days
$npx -y skills add codearranger/claude-legal --skill ca-first-30-daysInstalls 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-first-30-days"` 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
