product-management
AGENTS.md0 starsChanged 5 months agoMITView on GitHub
Authoritative contract for this folder. Designed for copying into any approved local or Git workspace, then splitting later with agents. Parent portable-mvp/ remains untouched reference baseline. Read this complete file before editing. Continue only in /Users/subramanianvittobh/Layer-A-Product-Task/five-file-structure. This folder is active transfer bundle; sibling portable-mvp/ is retained thirteen-file baseline and was not changed by five-file/UI work. Current checkpoint: Resume commands: Design references (reference only; do not download or execute): Preserve runnable local deterministic POC in exactly five source files: Generated local…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pptx-officialSkill
- prd-to-sdlcSkill
- y-score-readinessSkill
- cavemanSkill
- productowner-skillSkill
The file
Show its rules and text
We split this agents.md into the rules it gives an agent
13 rules. About 2 are common, 5 are distinctive, and 6 are very specific to this project.
≈2
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Read this complete file before editing.
- Distinctive: line 20
Never open external Chrome/Playwright for UI review.
- Very specific: line 21
Before serving, confirm port 8080 is serving this folder, not sibling baseline.
- Common: line 90
No network, downloads, installs, remote Git/API operations, browser automation, credentials, or private enterprise data.
- Distinctive: line 91
Never execute pasted, downloaded, or unknown code.
- Common: line 92
Never store secrets, tokens, passwords, private keys, customer data, account numbers, or card numbers.
- Very specific: line 100
Keep index.html separate for direct UI editing.
- Very specific: line 103
Treat API/user text as untrusted.
- Distinctive: line 106
No browser automation or saved screenshots/images for review.
- Very specific: line 111
Never edit parent portable-mvp/ while working here unless user explicitly asks.
- Distinctive: line 113
Do not delete embedded resources until exported equivalents validate and callers use new paths.
- Distinctive: line 114
No additional permanent file in this folder without explicit scope change.
- Very specific: line 129
No production SSO/RBAC, secret store, encrypted database, remote models, live market/news/legal research, hostile-code containment, …
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Layer A + Part B — Five-File Transfer Bundle
Authoritative contract for this folder. Designed for copying into any approved local or Git workspace, then splitting later with agents. Parent portable-mvp/ remains untouched reference baseline.
Cursor resume memory — 2026-08-13
Read this complete file before editing. Continue only in /Users/subramanianvittobh/Layer-A-Product-Task/five-file-structure. This folder is active transfer bundle; sibling portable-mvp/ is retained thirteen-file baseline and was not changed by five-file/UI work.
Current checkpoint:
- Bundle contains exactly five source files:
AGENTS.md,layer_a.py,layer_a_config.json,index.html, andtest_layer_a.py. Do not add files before transfer. - Latest executable evidence:
python3 layer_a.py validate→PASS,5/5;python3 -W error::ResourceWarning -m unittest -v→60/60 OK; JavaScript syntax and Python compile checks pass. - Part A remains honestly
INCOMPLETE: 18 gatesVALIDATED; Gate 18EXTERNAL_SIGN_OFF. Part B remains 8/8VALIDATED_POC. Plugin remainsUNSIGNED. - UI was reshaped in
index.htmlusing Anthropicfrontend-designguidance plus clean-room structural ideas from Figma Sidebar Navigation Starter Kit and Dmitry Sergushkin's sidebar-navigation case study. No external component source, package, CDN, font, icon, image, or executable code was imported. - Active UI direction: evidence-first product workspace; light neutral canvas; ink text; blue actions; green evidence state; flat cards; restrained density; serif display headings; system sans body; monospace utility labels.
- Sidebar direction: 248px expanded rail, 60px collapsed rail, grouped
Understand/Decide/Advanceditems, visible active state, completion marks, mobile drawer, quiet background, local/mock status in footer. - Fixed defects: stale legacy route normalized to
pb_portfolio; legacy AI panel hidden; duplicate top-bar Readiness/Copilot actions removed; desktop collapse grid fixed; collapsed labels hidden; desktop sidebar close button fixed; mobile backdrop stacking fixed (#sidebar-backdropbelow#left-sidebar) so transparent overlay no longer steals sidebar clicks. - Normal navigation exposes Part B experiences plus Plugin and Compare. Large legacy PIF Engine rendering code still exists dormant/unreachable inside
index.html; remove only through behavior-preserving refactor with tests. - User reports UI had many issues. Latest sidebar click defect is fixed in code, but visual acceptance is not claimed. Continue with user-observed issues one at a time and verify in Cursor/VS Code embedded preview.
- Never open external Chrome/Playwright for UI review. Never create or save screenshots/images. User reviews through embedded editor browser only.
- Before serving, confirm port 8080 is serving this folder, not sibling baseline. Expected page title:
PIF — Evidence Workspace; visible brand:PIF Evidence.
Resume commands:
cd /Users/subramanianvittobh/Layer-A-Product-Task/five-file-structure
python3 layer_a.py validate
python3 -W error::ResourceWarning -m unittest -v
python3 layer_a.py serveDesign references (reference only; do not download or execute):
https://github.com/anthropics/skills/blob/main/skills/frontend-design/SKILL.mdhttps://www.figma.com/community/file/1090687088484431239/sidebar-navigation-starter-kithttps://www.dmitrysergushkin.com/blog/case-study-research-sidebar-navigation
Goal
Preserve runnable local deterministic POC in exactly five source files:
AGENTS.md— transfer contract, usage, security, limitations.layer_a.py— runtime, APIs, validators, embedded-resource export.layer_a_config.json— all contracts/config plus embedded plugin, MCP, and Product Discovery skill resources.index.html— dependency-free same-origin frontend.test_layer_a.py— executable evidence.
Generated local state, caches, Git metadata, and later unpacked resources are not part of five-file transfer bundle.
Commands
python3 layer_a.py validate
python3 -W error::ResourceWarning -m unittest -v
python3 -m py_compile layer_a.py test_layer_a.py
python3 layer_a.py serveReview URL: http://127.0.0.1:8080/.
Expand after transfer
Embedded plugin resources stay inspectable as JSON/text inside layer_a_config.json. Export into separate folder without overwrite:
python3 layer_a.py unpack --unpack-dir ./expanded-resourcesWrites only:
plugin.jsonmcp.jsonskills/product-discovery/SKILL.md
Command refuses existing targets and refuses writing into five-file bundle. Agents may later split documentation, configuration, runtime modules, frontend assets, tests, Docker files, or CI files inside destination Git repository after explicit scope approval.
Current truth
- Python standard library only.
- Localhost-only server and same-origin
/api/*frontend calls. - Deterministic mocked/redacted research and model behavior; no real LLM or live research.
- First-party SQLite state under generated
.layer-a-state/. - Part A: 18 validated gates; Gate 18 remains
EXTERNAL_SIGN_OFF; overallINCOMPLETE. - Part B: 8/8 experiences
VALIDATED_POC. - Embedded Agent Plugin remains
UNSIGNED; exact local approval still required. - Five physical transfer files plus three embedded/exportable plugin artifacts.
Security boundary
- No network, downloads, installs, remote Git/API operations, browser automation, credentials, or private enterprise data.
- Never execute pasted, downloaded, or unknown code.
- Never store secrets, tokens, passwords, private keys, customer data, account numbers, or card numbers.
- External providers, adapters, live research, remote MCP/A2A, authentication, hosting, and cloud persistence remain disabled.
- SQLite is local POC persistence, not encrypted enterprise storage.
- Signatures, popularity, publisher identity, and local tests do not prove safety or production readiness.
- Remote action, dependency install, destructive action, credential use, or production connection needs explicit action-specific approval.
Frontend contract
- Keep
index.htmlseparate for direct UI editing. - Vanilla HTML/CSS/JavaScript only; no CDN, npm, framework, remote font, image, icon, analytics, or absolute runtime URL.
- Requests stay relative same-origin
/api/*. - Treat API/user text as untrusted. Prefer
textContent; escape fixed-template interpolation. - Preserve keyboard focus, semantic labels, request/error/empty/blocked states, reduced motion, and 320/768/1024/1440 layouts.
- Product-user view hides manifests, MCP, task packets, trust internals, and storage JSON unless advanced/admin detail is deliberately opened.
- No browser automation or saved screenshots/images for review. User views UI through VS Code Simple Browser.
Ownership and migration
- Five-file folder is independent alternative, not replacement for parent baseline.
- Never edit parent
portable-mvp/while working here unless user explicitly asks. - Preserve behavior before structural splitting. Use expand → migrate → verify → contract.
- Do not delete embedded resources until exported equivalents validate and callers use new paths.
- No additional permanent file in this folder without explicit scope change.
Validation gate
Change is complete only when:
python3 layer_a.py validatereportsPASS, expected/actual5;- full unit suite passes;
- Python compile passes;
- frontend remote-dependency scan returns no matches;
- unpack test proves three resources export without overwrite;
- parent five authoritative source hashes remain unchanged.
Honest limitations
No production SSO/RBAC, secret store, encrypted database, remote models, live market/news/legal research, hostile-code containment, distributed workers, cloud hosting, remote plugin installation, verified signatures, enterprise approval, or deployment certification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

