Adam S
Community@adam-s
Adam S builds Next.js dashboards on reverse-engineered website APIs, with skills for traffic capture, proxy routing, debugging, testing, and EC2 deployment.
Agent Skills by Adam S
Showing 10 vetted skills indexed across 2 GitHub repositories.
adam-sapp
Builds a complete application from a plain-language description through interactive discovery and dashboard construction.
adam-sdashboard-builder
Build Next.js dashboard pages that consume domain proxy API endpoints.
adam-sdebug-logs
Diagnose runtime bugs by iteratively adding targeted DEBUG() log calls and reading output.
adam-sci-check
Runs local CI checks and verifies GitHub Actions status for the current branch.
adam-sinstruction-dashboard-tuning
Map a website's API surface and generate proxy routes across transports.
adam-ssystematic-testing
Validates multi-layer architectures bottom-up by testing domain plugins, proxy routes, browser capture, and dashboard UI independently.
adam-sec2-deploy
Automate EC2 deployments and Docker Compose workflows with health checks.
adam-sinstruction-tuning
Iteratively run sub-agents, inspect results, and fix .claude/ instruction files.
adam-svisual-dev
Coordinate visual QA for dashboards using Patchright-based screenshot checks.
adam-sapi-discovery
Discover website APIs by capturing browser traffic and generate typed proxy routes.
Frequently Asked Questions About Adam S
FAQPage SchemaWhat tasks can I accomplish with Adam S's skills?▼
You can discover any website's API by capturing browser traffic, generate typed domain plugins and proxy routes, build Next.js dashboards that consume those endpoints, debug WebSocket and proxy failures with targeted logging, validate multi-layer architectures bottom-up, run CI checks, and deploy to EC2 with Docker Compose.
Who are these skills designed for?▼
Developers building data-driven dashboards on top of third-party websites that lack public APIs. It suits engineers who need to reverse-engineer a site's data transport, create typed API clients, render comparison or search interfaces, and maintain the full stack from traffic capture through deployment.
How does the typical build process work?▼
Start with the app skill: describe the product in plain language, answer clarifying questions, and let discovery agents map the target site's API surface. Then dashboard-builder creates Next.js pages calling /api/<domain>/ proxy routes, systematic-testing validates each layer, and ci-check verifies GitHub Actions before release.
How do I debug failing proxy routes or empty traffic captures?▼
Use the debug-logs skill, which applies iterative DEBUG() runtime logging: add targeted logs at the browser, proxy, or WebSocket layer, read the output, narrow the search, and repeat until the root cause is found. Logs are cleaned up after the fix is confirmed.
What are the prerequisites and deployment requirements?▼
You need a Next.js project with domain proxy endpoints, GitHub Actions for CI verification, and AWS EC2 with Docker Compose for deployment. Visual QA uses Patchright-based screenshot checks, and instruction tuning relies on .claude/ configuration files for sub-agent iteration.