What is liferay-dummy-factory CLAUDE.md?

A set of instructions for coding agents working on liferay-dummy-factory, a Liferay workspace containing Java portlets, a React portlet, and integration tests. It explains where task-specific rules, technical details, decisions, and commands are kept.

Use it before coding, testing, debugging, or reviewing changes in the workspace, especially when working with its rules, documentation, architecture decisions, or workflow APIs.

It routes each task to the right project rules and records important contracts that can otherwise fail silently. This helps agents avoid breaking input handling, shared sources of truth, or creation workflows.

How yasuflatland-lf/liferay-dummy-factory configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to yasuflatland-lf/liferay-dummy-factory. 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/yasuflatland-lf/liferay-dummy-factory/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/yasuflatland-lf/liferay-dummy-factory

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/yasuflatland-lf/liferay-dummy-factory/claude-md/github.svg)](https://agentmods.dev/instructions/yasuflatland-lf/liferay-dummy-factory/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/yasuflatland-lf/liferay-dummy-factory/claude-md"><img src="https://agentmods.dev/badge/instructions/yasuflatland-lf/liferay-dummy-factory/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/yasuflatland-lf/liferay-dummy-factory/claude-md"><img src="https://agentmods.dev/badge/instructions/yasuflatland-lf/liferay-dummy-factory/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 734 This file is loaded in full into every session.

When invoked 734 The same file — it is already loaded in full.

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.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00734	$0.00734
Opus 5	$0.00367	$0.00367
Sonnet 5	$0.00147	$0.00147
Haiku 4.5	$0.00073	$0.00073

Measured 11d ago against content hash 527fb268241d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

liferay-dummy-factory CLAUDE.md 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 11d 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.md · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

liferay-dummy-factory

Liferay DXP 2026.Q1.9-LTS Workspace: MVCPortlet + React portlet + Spock integration tests against liferay/dxp:2026.q1.9-lts.

Routing — read the matching L2 file for the task you're starting

Feature / refactor / general code change → .claude/rules/writing-code.md · Tests → .claude/rules/testing.md
Bug or test-failure investigation → .claude/rules/debugging.md · PR / code-quality review → .claude/rules/code-review.md

Where to find concrete details and history

docs/details/ — concrete commands, selectors, version pins, API constraints (read on demand); workflow-api.md is SoT for site.create / organization.create / taxonomy-only startup fallback. docs/ADR/ — past decisions.
.claude/plan/ — gitignored scratch for orchestration plans; never lands in a diff.

Core contracts — break these and things go silently wrong

Input boundary policy — reject user input at the boundary; sanitize external-generated data. Never mix the two strategies.
Single source of truth — every fact, rule, or contract lives in exactly one file. Other files link to it.
Creator + batch response contract — *Creator classes wrap per-entity work in TransactionInvokerUtil.invoke + throws Throwable and return {success, count, requested, skipped, error?, items} with strict success := created == requested; error MUST be set whenever success == false. Detail in .claude/rules/writing-code.md.
JSONWS-first verification — test post-conditions through /api/jsonws/..., not Playwright UI navigation. Detail in .claude/rules/testing.md.
jakarta.portlet 4.0 — DXP 2026.Q1.9-LTS uses jakarta.portlet.* imports and jakarta.portlet.version=4.0 component properties. JSP taglib URI stays http://xmlns.jcp.org/portlet_3_0 (JCP namespace). See docs/ADR/adr-0008-dxp-2026-migration.md.
data-testid is mechanically named — ${entityKey}-${kebab(field)}-${typeSuffix}. Do not invent ids; follow the contract in .claude/rules/writing-code.md.
One package manager per repo — yarn.lock only. Never coexist with package-lock.json.

Read the full file on GitHub · 36 lines

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.

11d ago First seen · 36 lines · 734 tokens per session scan A 527fb268241d

Subscribe to this mod's changes

liferay-dummy-factory CLAUDE.md is an instructions file published in the GitHub repository yasuflatland-lf/liferay-dummy-factory (50 stars, last pushed today), licensed MIT. It adds 734 tokens to every session, about $0.0037 per session on Opus 5. 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-30.

debug debugging-tool debugging-tools dummy-data generator liferay

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

liferay-dummy-factory: Instructions file for Claude Code