PXOS
madebypx/PXOS/llms-full.txt
First-Class Citizens Unlike traditional developer frameworks that treat user interfaces merely as frontend code syntax, PXOS embeds **Product Design, Human-Computer Interaction (HCI), and UX Strategy** directly into
How real projects summarise themselves for language models.
madebypx/PXOS/llms-full.txt
First-Class Citizens Unlike traditional developer frameworks that treat user interfaces merely as frontend code syntax, PXOS embeds **Product Design, Human-Computer Interaction (HCI), and UX Strategy** directly into
minjikim89/make-me-unicorn/llms.txt
products. It checks a codebase against a 670-item launch checklist across 15 categories — frontend, auth, billing, security, SEO, legal, observability, deployment, monitoring, growth, and more — organized into 6 named
patalbansishashank/hyponoia/docs/llms.txt
native executable with an authenticated integration asset; the UI variant adds one content-addressed frontend pack. All processing is local — the embeddings run on-device; there is no embedded
Pentagonal-ai/pentagonal/public/llms-full.txt
audits. (3) Full lifecycle — generate, audit, fix, and deploy from one platform. --- ## Technical Stack - **Frontend:** Next.js 15, React 19, TypeScript - **Styling:** Vanilla CSS with design tokens - **Auth:** Supabase Auth (OAuth
pixel-educacao/pixel-aihub-skills-public/llms-full.txt
reduzir erros de LLM: don't assume, minimize code, surgical changes, verifiable success. 03 | frontend-design | foundation-security | essential | intermediate | medium | ready | auto | UI production-grade. Evita "estética IA genérica
proveo-ca/orrery/llms-full.txt
human approval. - **@architect** — designs before code. Must be consulted for non-trivial work. - **@backend / @frontend / @devops** — domain specialists. - **@adversarial-reviewer** — finds every problem in a diff. No fixes on first
rdhawladar/claude-code-fullstack-starter/llms.txt
GitHub template that bootstraps a Claude Code project with five specialist AI subagents (architect, frontend, backend, QA, code reviewer), pre-configured workflows, coding standards, and architecture documentation — built specifically
rlakamraju/accessible-ai/llms.txt
site: Crawl and audit all pages - analyze_codebase: AST-level static analysis of a frontend project - import_audit_results: Import Chrome Extension findings - map_violations_to_source: Map runtime violations
Roughn3ck/ExecutiveMind/llms.txt
compliance. - Aria (Site-Shaper) — Web dev, SEO, brand guardian. - Dash (UI/UX) — Dashboard and frontend. - Vault (Treasury Guardian) — Privacy sentinel, deny by default. - Scout (Market Intelligence) — Speed is signal, alpha from
sandraschi/kicad-mcp/llms.txt
dashboard | | `justfile` | bootstrap, serve, test, e2e | ## Ports | Port | Service | |------|---------| | 11016 | Backend (FastAPI + FastMCP) | | 11017 | Frontend (Vite dev) | | 11018 | Legacy KiCad TCP bridge | ## Quick Start ```powershell uv sync --extra ipc just
sandraschi/kubernetes-mcp/llms-full.txt
cluster. ## Tech Stack - **Backend**: Python 3.12+, FastMCP 3.4.4+, FastAPI, uvicorn, kubernetes client SDK - **Frontend**: React 19, Vite, Tailwind CSS v3, Zustand, Lucide Icons - **Ports**: Frontend 11184, Backend 11183 (changed
sandraschi/kubernetes-mcp/llms.txt
ingresses) and local Minikube control VM automation. ## Architecture - **Backend (Port 10811)**: Python/FastAPI backend proxy. - **Frontend (Port 10810)**: React/Vite companion dashboard (Zinc/Blue Dark theme). - **Transport**: Stdio (Claude Desktop) and HTTP. ## Documentation
sandraschi/kyutai-mcp/llms-full.txt
Fleet blueprint layout: sidebar + topbar + main + logger panel + chat modal - Webapp ports: - backend: 10924 - frontend: 10925 Tools ===== moshi_ops(operation, include_env=False) Operations: - status: server runtime and platform summary
sandraschi/learnbot-mcp/llms.txt
platform_send` - platform bridge (speech, etc.) ## Ports - Backend: 11101 (REST API) + stdio (MCP) - Frontend: 11102 (Vite dev) See `llms-full.txt` for full reference
sandraschi/norirobotics-mcp/llms-full.txt
behind a verified bridge). ## Ports 11970 backend (FastAPI + FastMCP HTTP /mcp + REST /api/*), 11971 frontend (Vite React). ## REST endpoints (fleet 1E) GET /api/health, GET /api/status (uptime, tool_count, session
sandraschi/resolume-mcp/docs/llms-full.txt
RESOLUME_PATH | (none) | Path to Resolume Arena executable | ### Ports | Port | Service | Notes | |------|---------|-------| | 11139 | Frontend (Vite dev) | Web dashboard | | 11140 | Backend (Starlette) | REST + MCP HTTP | | 7000 | OSC In | Resolume receives
sandraschi/resolume-mcp/llms.txt
real-time performance. ## Quick Info - Entry point: `python -m resolume_mcp` - Backend port: 11140 - Frontend port: 11139 - OSC ports: 7000 (in), 7001 (out) ## Tools - help: Multilevel help system - status: System
seomarlboro/digmyname/public/llms.txt
compared: Namecheap, Cloudflare, Porkbun, GoDaddy, Spaceship, and OVHcloud (6 total). - Tech stack: React + Vite frontend, Lovable Cloud (Supabase) backend with Edge Functions for availability checks and price aggregation
Shaharamir/grow-payments-mcp/data/llms-full.txt
# Grow Payments — Full Documentation (llms-full.txt) All pages scraped from https://grow-il.readme.io. Generated for LLM
simongonzalezdc/GameStory-Lab/llms.txt
versioned concept history - export GDD, pitch, and technical documentation as markdown - run a React frontend, Node/Express backend, Prisma/PostgreSQL database, Redis queue, and optional local Ollama models ## Install / use Install with
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.