sahin.io

All skills and agents

standing-rules

The owner's standing rules for sahin.io/angel-investments and how to record a new one. Use whenever the owner says "always", "never", "this is a rule", "from now on" or "every time", before editing CLAUDE.md, and when unsure whether an owner preference applies.

Source file
.claude/skills/standing-rules/SKILL.md

Standing rules

Recording a new rule

When the owner says "always", "never" or "this is a rule", do this in the same turn. A rule that lives only in chat is lost.

  1. Write it into the skill that owns that work (create one if none fits), and list it below.
  2. If it needs a reviewer, add or update an agent in .claude/agents/.
  3. Enforce it some other way when you can: a test in server/*.test.ts, a gate or validator step, or a hook (update-config skill; user-level ~/.claude/settings.json when the rule is about more than this repo).
  4. Manus reads skills/. Point at the Claude skill there; don't copy it.
  5. Save it to agent memory.
  6. Keep CLAUDE.md thin (owner, 2026-10-11): at most a one-line pointer. server/claude-md-thin.test.ts fails when it grows past its limit.

The rules-keeper agent does steps 1–6 for you.

Rules

  • Only ever work in this repo (owner, 2026-10-13: "we only work in web-angel-investments"). Never edit, commit, push or deploy another repo (~/Code/sahin/web, web-v0, pef-austin-recommendations or any sibling under ~/Code/sahin/). If a screenshot or request concerns UI that only exists elsewhere, say where it lives and stop. A terse "deploy" is never permission to touch another repo (a6bb0f4b was pushed to ~/Code/sahin/web that way and rejected). Enforced by the PreToolUse hook scripts/hooks/only-this-repo.mjs (.claude/settings.json) and server/only-this-repo-hook.test.ts; see ship-to-production and private-data-boundary.
  • Keep CLAUDE.md thin; rules live in skills, agents, tests and hooks (owner, 2026-10-11).
  • Always keep angel-investments-performance (owner, 2026-10-11), the private Angel Simulator: never delete, archive, history-rewrite or scrub it. Enforced by a user-level hook. Details: private-data-boundary skill.
  • Private deal data and AngelList links never leave the Simulator (owner, 2026-10-11): private-data-boundary skill, private-data-auditor agent, server/private-deal-data.test.ts, pnpm privacy:bundle.
  • Only one IRR, the general one (owner, 2026-10-11: "IRR is ok, general IRR is ok, only one IRR is allowed, which is general"). The portfolio-wide figure lives only in data/portfolio-performance.yaml (generalIrr) via shared/portfolioPerformance.ts; copy uses {irr}. No per-company or per-deal IRR, no second IRR figure: private-data-boundary skill, server/general-irr-single-source.test.ts.
  • Default order is always by valuation, on every portfolio page (owner, 2026-10-12: "always default order should be always by valuation — in every portfolio page"). Wherever a portfolio company list has a default order (hub theme views client/src/components/views/*View.tsx, React pages client/src/publicPages/*Page.tsx, static lists via server/companyListControls.ts, VC-style pages) it is the valuation order: sortCompaniesByMarketCap (client/src/data/portfolioData.ts) on the client, sortByMarketCap on the server. Alphabetical order is only an explicit user-chosen sort, never the default; ties / no value fall back to name; no company value is written into markup. Skills: theme-system, page-vc-portfolios, project-architecture. Tests: server/portfolio-default-order.test.ts (fails on a default a.name.localeCompare(b.name) sort), server/company-list-controls.test.ts.
  • Never show a VC firm's logo or brand mark in a theme (owner, 2026-10-11: "this is a rule"). VC-inspired themes copy a firm's layout, type, colors and image style only; where the firm's page shows its logo, use Sahin's SahinMark (client/src/components/views/publicThemePrimitives.tsx). The theme gallery has no firm logo images.
  • No source notes or "(sourced)" labels on public pages (owner, 2026-10-11). Company values read "Market cap $2.21T" with the amount linking to its source (tooltip "Publisher, Mon YYYY") via shared/publicCompanyValueFormat.ts / server/publicCompanyValue.ts; research text passes through shared/sourceNotes.ts; never write "(Publisher, Month)" or "(sourced)" in copy.
  • Content lives in YAML + Markdown, not in code (owner, 2026-10-11: "no html code, yaml + markdown only"): page-content-yaml skill; server/content-in-yaml.test.ts fails when a page file gains inline copy (baseline content/migration/inline-copy-baseline.json).
  • Never noindex, never nofollow: a page has its own content, or it does not exist (owner, 2026-10-16: "Never no index, make the pages more unique (this is a rule)", then "never do noindex, nofollow. (dont create the page or create the content for each page)"). No noindex or nofollow anywhere: robots meta, X-Robots-Tag, or a link's rel. A thin or duplicate page gets unique, sourced content (facts, sources, its own angle); a page that can't have its own content is not created, and an old URL to it 301s to the closest real page. Done on 2026-10-16: the 837 legacy noindex routes (518 news items, 314 founders, 5 duplicate Sub-Category investor directories) are no longer created and each old URL 301s to the closest real page (manifest.retired in server/seoRouteManifest.ts, materialized by server/legacyRedirects.ts), with nothing linking to them; and every cited source is a plain direct link with the publisher as anchor and no rel (the /sources/{id} hop pages are gone; an old /sources/{id} URL 301s straight to its source; a source on a private host such as AngelList, Wellfound, Airtable or Google Drive shows its publisher unlinked, private-data-boundary). server/never-noindex.test.ts fails on any noindex route, code path returning 'noindex', retired URL that does not 301 to a real route, or source file containing nofollow; scripts/validate-public-seo-build.mjs fails on nofollow or a /sources/ link in any built page. Thin pages are found by scripts/seo-aio-audit.mjs. Skills: seo-audit, seo-head-and-schema, page-founders, page-news, page-taxonomy, page-status-sectors-markets, new-react-page; agent seo-aio-auditor.
  • Short company names come from data/company-display-names.yaml (e.g. Kraken). Run node scripts/company-display-names.mjs after editing it; the Airtable sync re-applies it. Slugs never change.
  • Counts come from one source of truth: portfolio-counts-single-source skill, server/portfolio-status-single-source.test.ts.
  • Write public URLs in full (sahin.io/angel-investments/anthropic/angel-investors): public-url-conventions skill.
  • Airtable updates use the Manus view only: airtable-manus-sync skill.
  • Auto-ship mode is ON: ship-to-production skill. "auto-ship off" pauses it.
  • Every change runs the deploy gate: deploy-gate skill.
  • Every visible change shows before/after screenshots (desktop + mobile): ui-before-after skill.
  • The owner decides where each visual regression run happens: small on GitHub Actions, big locally (owner, 2026-10-17: "all visual regression tests should be run in the local or github actions (i will decide which one) if it is small, github actions and if it is big then in local"). Before any visual run (pnpm test:visual, the Visual regression workflow, pnpm parity), give its size and a recommendation and wait for the owner's pick. The workflow is manual dispatch only. ui-before-after skill (sizes and commands), server/visual-regression-placement.test.ts, user-level skill visual-regression-placement.
  • Lessons that fit every project go in user-level skills (~/.claude/skills/, owner, 2026-10-17: "things that can be used in every project should be in skills or agents and in claude.md thin"). This repo's skills keep its own details and name the user-level skill. User-level skills so far: keep-claude-md-thin, local-gate-ci-parity, visual-regression-placement.