remembra / landing
remembra-ai/remembra/landing/llms.txt
session hooks are verified. So are Gemini CLI's, Qwen Code's and Kimi Code's: each was run against the real tool. Codex runs a hook only after
How real projects summarise themselves for language models.
remembra-ai/remembra/landing/llms.txt
session hooks are verified. So are Gemini CLI's, Qwen Code's and Kimi Code's: each was run against the real tool. Codex runs a hook only after
tamdogood/parler-protocol/llms.txt
Engineering guidelines](/docs/engineering-guidelines.md): the contract every change follows (hard gates, invariants, definition of done). - [Code review guidelines](/docs/code-review-guidelines.md): how every change is reviewed (verified findings, severity ladder). - [CI/CD](/docs/ci-cd.md): pipeline
allemaar/open-skills/llms.txt
before any work begins. — triggers: /plan-create, make a plan, plan this out, design before coding - plan-deep-dive [protocol.yon] — Phase-by-phase deep inspection of any multi-phase plan — stop
mick-gsk/drift/llms.txt
changed files - Git change detection failure This gives AI coding agents an immediate go/no-go signal after each edit — no manual review needed. ## Use Cases - Detect pattern fragmentation: same concern implemented
odyth/red-queen/docs/llms.txt
workers through a configurable SDLC pipeline: spec writing, > automated plan review, human spec review, coding, code review, testing, > and human review. Phases, skills, and gates are declared in > `redqueen.yaml`. Open
odyth/red-queen/llms.txt
Code or Codex workers (selectable per phase) through a > configurable SDLC pipeline (spec → plan review → code → review → test → > human review) with human-in-the-loop gates; issues linked as blockers
peacprotocol/peac/llms.txt
cross-runtime systems. > Portable signed records anyone can verify offline. > Current release: v0.16.4 > Last reviewed: 2026-06-24 ## What is PEAC PEAC Protocol provides cryptographically signed, offline-verifiable interaction records
ariaxhan/kernel-claude/llms.txt
function budgets, regression diffs, and a project-owned verify gate. - `/kernel:review` · `$kernel:review`: code review with a deterministic scanner lane and a refutation pass; APPROVE, REQUEST CHANGES, or COMMENT
Brandcode-Studio/brandsystem-mcp/llms.txt
Figma files, or heads and wants them machine-readable - User wants Claude Design, Claude Code, Cursor, or Windsurf to ground on their brand via a direct local MCP connection
hongnoul/gwae/llms.txt
Homebrew: `brew install hongnoul/tap/gwae`. gwae exists for people who run several coding agents (Claude Code, Jcode, Codex CLI, OpenCode, Gemini CLI, Aider) in parallel on a Mac. tmux and Zellij
jedijashwa/pullmark/site/llms.txt
rendered diffs with word-level highlights. It is built for > reading and reviewing the Markdown that coding agents and teams produce: > plans, specs, design docs, ADRs, runbooks. Key facts: macOS
oyi77/1ai-skills/llms.txt
response, zero trust, cloud security, API security, OT/ICS security - **Development** (90 skills) — TDD, debugging, code review, PRD, spec-driven development, context engineering, browser testing, Git workflows - **Content** (62 skills) — Video
alexpilotto/uxon-ai/llms.txt
poll generation jobs. - Import coded page bundles from Claude Code, Codex, Cursor, or v0. - Publish, duplicate, and review landing pages through API commands. - Launch A/B/n experiments across UXON pages, external
antoinedc/MantaUI/website/llms-full.txt
talks to your model provider and to APNs for push fanout. Nothing else. - ✓Your code stays on your box. Transcripts, uploads, secrets and configuration live on your machine. The only
antoinedc/MantaUI/website/llms.txt
mobile](https://mantaui.com/claude-code-mobile): a native iPhone app, full transcript, approvals, dictation. - [Claude Code remote](https://mantaui.com/claude-code-remote): running the agent on a VPS or home server. - [Open source
RayforceDB/raysense/site/llms.txt
edited repositories. When agents commit dozens of changes per hour, per-diff code review cannot track whether the codebase shape is improving or degrading. Raysense closes that gap with
vivekchand/flywheel.md/llms-full.txt
build, release, and evolve. Why now: when agents write the code, coding stops being the bottleneck. Verification, review, and ownership become it, and the processes built to protect scarce engineering
d-oit/rust-2026-template/llms-full.txt
Generated HTML review and analysis output (ignored) ├── schema/ # JSON Schema definitions for config/API contracts ├── scripts/ # Automation scripts for quality gates and releases ├── AGENTS.md # Canonical instructions for AI coding agents ├── llms.txt
event4u-app/agent-config/llms.txt
holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review. agent-docs-writing: Use when reading, creating, or updating agent documentation, module docs
Rul1an/assay/llms.txt
Assay > Policy-as-code for MCP agents: a deterministic, fail-closed gate for MCP tool calls, with kernel-level (eBPF/LSM) enforcement on Linux and offline-verifiable evidence bundles. CI-native
A markdown file at a website's root that gives language models a short guide to the site and links to the pages worth reading.
The same idea with the content included, so an agent can read the documentation in one request.
Agents and tools that fetch documentation on someone's behalf. It's a proposal, not a standard, and support varies.
Start with a one-line summary, then sections of links with a sentence each. The examples here show what real projects do.