alexop.dev valid
alexop.dev
A Personal Blog from a simple web developer
For agents: Personal blog by a web developer on coding agents, Claude Code, TypeScript and Effect, with full blog content in llms-full.txt.
coding agentsclaude codetypescriptvibe engineeringcode review
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T14:37:13.130Z. Cached copy · Source on alexop.dev
# alexop.dev
> A Personal Blog from a simple web developer
## Full Documentation
- [Full Blog Content](https://alexop.dev/llms-full.txt): Complete blog posts with full content for deep context.
## Blog
- [Learning from pstack: Build Your Own Reliable Coding Agent Stack](https://alexop.dev/posts/learning-from-pstack): The written version of my TypeScript Meetup Munich talk. What pstack teaches about planning, implementation, review and verification, and how to give your own agent a verification skill that proves its work.
- [I think software teams will shrink to 2-4 people plus agents](https://alexop.dev/posts/software-teams-will-shrink-to-2-4-people-plus-agents): This post follows one ticket through a German Scrum team and shows where that path breaks.
- [The death of the software developer](https://alexop.dev/posts/the-death-of-the-software-developer): In 2026, the developer who writes every line by hand will disappear. What still matters: knowing what to build, caring for a codebase, and being a high-agency generalist.
- [The Dirty Flag Pattern, Explained with Snake](https://alexop.dev/posts/dirty-flag-pattern-snake): Stop redrawing what didn't change. Learn the dirty flag pattern with an interactive Snake game, then see where the same idea hides in Vue's computed.
- [pstack's Playbooks, Explained as Factorio Factories](https://alexop.dev/posts/pstack-playbooks-as-factories): pstack's poteto-mode picks one of 23 playbooks for every task. I built ten of them as interactive Factorio-style factories, so you can see why a bug fix, a refactoring and a hillclimb each need a differently shaped factory.
- [Run Only the Playwright Tests Your Change Can Affect](https://alexop.dev/posts/run-only-affected-playwright-tests): Feature-based architecture can shorten your E2E feedback loop. A working Nuxt example with dependency-aware test selection and GitHub Actions.
- [How I made exercise icons with Codex and ChatGPT](https://alexop.dev/posts/building-workout-app-ai-exercise-icons): I used ChatGPT and Codex image generation to create matching exercise icons for my workout app. See the reference image and before-and-after screenshots.
- [Hexagonal Architecture in Vue: Where to Put Your Code and Why](https://alexop.dev/posts/hexagonal-architecture-vue): Learn what belongs in Vue components, composables, the application core, and adapters. Use ports and adapters to make rules easier to test and changes easier to contain.
- [Enforce Tailwind CSS Design Tokens in Vue with @shadcn/lint](https://alexop.dev/posts/enforce-tailwind-design-system-shadcn-lint): Catch raw colors, arbitrary values, and component overrides in Vue with @shadcn/lint. Includes ESLint setup and interactive before-and-after examples.
- [What my first Tacon taught me: give AI a better testing process and know your audience](https://alexop.dev/posts/my-first-time-at-tacon): Reflections from my first Tacon: testing talks, speaking to a QA audience, and building better AI-assisted testing work
…
Related sites
Find similar publishers by meaning →
Other listed sites in Personal sites and blogs. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ito.com | Joi Ito's Web | documentation Education Personal sites and blogs | — | 64 | ✓ | ✓ | |
| tomtunguz.com | Tomasz Tunguz | informational Personal sites and blogs | US | 64 | ✓ | ✓ | |
| ctrl.blog | Ctrl blog | documentation Personal sites and blogs | US | 63 | ✓ | ✓ | |
| devsaran.com | GENERATED by websites/scripts/generate-llms-txt.mjs — do not edit by hand. | documentation Personal sites and blogs | — | 63 | ✓ | ✓ | |
| fs.blog | Farnam Street: Mastering the best of what other people have already figured out | informational Personal sites and blogs | — | 63 | ✓ | ||
| nvie.com | nvie.com | documentation Personal sites and blogs | US | 62 | ✓ | ||
| randalolson.com | Dr. Randal S. Olson | informational AI and machine learning Data and analytics +2 | US | 62 | ✓ | ✓ | |
| acharyaprashant.org | Acharya Prashant | documentation Personal sites and blogs | — | 61 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=alexop.dev · GET /v1/domain/alexop.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage alexop.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for alexop.dev:
1. POST https://agentwebmap.com/v1/sites/alexop.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://alexop.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/alexop.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/alexop.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.