Thomas Smestad
Community@tsmes
Thomas Smestad provides developer lifecycle skills covering feature specification, implementation planning, React/TypeScript review, atomic git commits, and browser-based testing.
Agent Skills by Thomas Smestad
Showing 8 vetted skills indexed across 1 GitHub repositories.
tsmesagent-browser
Automate browser navigation, form filling, screenshots, and data extraction via CLI commands.
tsmeslogical-commit
Create logically atomic git commits by staging individual diff hunks with conventional commit messages.
tsmesdocument
Write accurate, minimal documentation for code, features, and systems.
tsmesfeedback
Present completed work to users and convert their feedback into actionable next steps.
tsmesimplementation-plan
Generate codebase-aware technical implementation plans from approved feature specifications.
tsmesreview-ts-react
Reviews TypeScript and React code changes, diffs, and pull requests for defects and maintainability issues.
tsmesmanual-testing
Validates implemented features by exercising API endpoints with curl and frontend flows with agent-browser.
tsmesfeature-spec
Generate detailed feature specifications through codebase exploration and structured user discussion.
Frequently Asked Questions About Thomas Smestad
FAQPage SchemaWhat tasks can I accomplish with tsmes's skills?▼
You can produce feature specifications, generate implementation plans from approved specs, review React/TypeScript pull requests, create atomic conventional git commits, document code and systems, gather structured feedback, and manually test features using curl and browser interaction.
Who are these skills designed for?▼
These skills target software developers and engineers working in React/TypeScript codebases who need structured support across the delivery cycle: specification, planning, code review, commit hygiene, documentation, feedback collection, and manual feature verification.
How does the manual-testing skill verify features in practice?▼
It runs the application locally, exercises backend endpoints with curl requests, and verifies frontend behavior through the agent-browser skill, which navigates pages, fills forms, clicks buttons, and captures screenshots to confirm expected behavior.
What does the logical-commit skill do differently from a standard git commit?▼
It creates logically atomic commits using surgical staging, grouping changes by purpose rather than file structure, and writes conventional commit messages so each commit represents one coherent, reviewable unit of work.
What are the prerequisites for using the agent-browser skill?▼
The skill requires Bash access to run agent-browser via npx or a direct installation. It is invoked whenever tasks require programmatic web interaction such as scraping page data, logging into sites, or testing web applications.