AI skills &
vibe coding tips.
Practical tips for vibe coders, a growing collection of WYN skills, and local AI Collective events with Nick Cybela.
Free skills,
built by WYN.
I'm building a collection of reusable skills for working with AI. First up: a better way to edit AI-written drafts.
The first skill is in development. Its GitHub repository and installation instructions will be linked here when it is published.
/wyn-humanize
A writing skill to help turn generic AI drafts into clear, specific writing that sounds like you.
Inspired by Peter Yang's /no-ai-slop on GitHub (opens in a new tab).
In development
Tips for vibe coders.
Start where you are. Move from making it work to understanding why it works.
New
Get a small, useful thing working.
Describe the result, not just the idea.
Say who it is for, what they should be able to do, and what a finished result looks like. Include a real example.
Build one complete action first.
Start with a single working flow, such as submitting a form. Add the next feature after you have tried the first one yourself.
Save a checkpoint before a big change.
Ask your agent to explain what will change and save the working version in Git. Give each checkpoint a name you will recognize.
Intermediate
Make the working version dependable.
Bring evidence to a debugging session.
Share the exact steps, the expected result, the actual result, and any error message. Ask for the cause before accepting another rewrite.
Try the uncomfortable cases.
Test a narrow phone screen, a keyboard, an empty form, a long name, and a failed request. A happy-path screenshot is only one check.
Keep private work on the server.
API keys, permissions, and validation belong on the server. Ask your agent to show what a visitor can see and which checks run again after submission.
Advanced
Design for real users and real failures.
Turn acceptance criteria into checks.
Write down what must remain true, then test those behaviors. Review the diff as well as the demo before you release.
Make retries safe.
Decide what happens after a timeout or double-click. Use stable request IDs so retrying a payment, message, or job cannot quietly duplicate it.
Plan the handoff and the rollback.
Document configuration, limits, failure states, and how to restore the previous release. Review access controls and dependencies before a public launch.
Let's build
something local.
Duluth & Johns Creek, Georgia
I host AI Collective events in Duluth and Johns Creek. Come learn with other builders, share something you are working on, or help shape a future session.
Want to join, suggest a topic, bring a demo, or help host? Connect with me on LinkedIn and ask about the next event.
Explore The AI Collective
Organizer
Duluth & Johns Creek
A question, a project, or an idea for a meetup? I'd like to hear it.
Connect on LinkedIn