love-claude-code: Settings file for Claude Code

.claude/settings.json

love-claude-code is a settings file for Claude Code from ArtemioPadilla/love-claude-code. Its token cost is not measured, scanned A, original, MIT.

A configuration for a coding-agent setup with a Playwright automation server and a guard that enforces test-first development. TDD, or test-driven development, means writing a failing test before the code that makes it pass.

In plain words
What is it for?
Use it in TypeScript and React projects to control file changes, require tests for matching frontend and backend files, and support browser automation through Playwright.
Why use it?
It helps prevent application code from being changed before tests exist, while allowing the work to move through test, implementation, and cleanup stages.

Settings file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: names the TodoWrite tool.

This is ArtemioPadilla/love-claude-code's own configuration. It tells Claude Code how to work on love-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything love-claude-code configures →

One of 2 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 1 are separate, each on its own page.

Reuse

Borrowing it

Nothing to install: this file belongs to ArtemioPadilla/love-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ArtemioPadilla/love-claude-code/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/ArtemioPadilla/love-claude-code

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for love-claude-code

README.md
[![agentmods](https://agentmods.dev/badge/settings/artemiopadilla/love-claude-code/settings/github.svg)](https://agentmods.dev/settings/artemiopadilla/love-claude-code/settings)
Your own site
<a href="https://agentmods.dev/settings/artemiopadilla/love-claude-code/settings"><img src="https://agentmods.dev/badge/settings/artemiopadilla/love-claude-code/settings/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for love-claude-code

Your own site · 80×15
<a href="https://agentmods.dev/settings/artemiopadilla/love-claude-code/settings"><img src="https://agentmods.dev/badge/settings/artemiopadilla/love-claude-code/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

love-claude-code scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/settings.json · 58 lines

What it actually says

{
  "hooks": {
    "PreToolUse": [
      {
        "name": "tdd-guard",
        "description": "Enforce TDD principles before file operations",
        "matcher": "Write|Edit|MultiEdit|TodoWrite",
        "command": "tdd-guard",
        "timeout": 5000,
        "config": {
          "enabled": true,
          "testFramework": "vitest",
          "watchPatterns": [
            "frontend/src/**/*.ts",
            "frontend/src/**/*.tsx",
            "backend/src/**/*.ts"
          ],
          "excludePatterns": [
            "node_modules/**",
            "dist/**",
            "coverage/**",
            "**/*.test.ts",
            "**/*.spec.ts"
          ],
          "strictness": "medium",
          "allowRefactoring": true,
          "phases": {
            "red": {
              "allowedFiles": ["**/*.test.ts", "**/*.spec.ts", "**/*.test.tsx"],
              "message": "🔴 Red phase: Write failing tests first"
            },
            "green": {
              "allowedFiles": ["**/*.ts", "**/*.tsx"],
              "excludeFiles": ["**/*.test.ts", "**/*.spec.ts"],
              "message": "🟢 Green phase: Make tests pass with minimal code"
            },
            "refactor": {
              "allowedFiles": ["**/*.ts", "**/*.tsx"],
              "message": "🔵 Refactor phase: Improve code quality"
            }
          }
        }
      }
    ]
  },
  "mcpServers": {
    "playwright-automation": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-playwright"],
      "env": {
        "PLAYWRIGHT_HEADLESS": "false",
        "PLAYWRIGHT_BROWSER": "chromium",
        "PLAYWRIGHT_TIMEOUT": "30000"
      },
      "description": "Playwright browser automation for E2E testing"
    }
  }
}
Same file

What else settings.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 58 lines scan A 444841dc397c

Subscribe to this mod's changes

love-claude-code is a settings file published in the GitHub repository ArtemioPadilla/love-claude-code (5 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.