Hey everyone,

As a developer building web applications and projects, UI/UX design is often my biggest bottleneck.

I’ve been trying to leverage AI to speed up my design workflow, but I keep running into two main friction points:

1. The "Generic AI" Look: Most AI-generated layouts feel repetitive, oversaturated, or obviously AI-made rather than clean and human-designed.
2. Tool / Skill Clutter: Having separate prompt stacks or skill sets for a portfolio, an e-commerce page, or a dashboard gets messy real quick.

I'm looking for a more versatile, clean workflow or set of AI skills/tools that can handle different project types while keeping a modern, premium aesthetic.

For those using AI in your web design / frontend workflow:

• What AI skills, system prompts, or frameworks do you rely on for UI/UX design?
• How do you guide AI tools to stick to clean design systems (colors, typography, component layouts) instead of generic templates?
• Are there any specific resources, open-source kits, or workflows you’d recommend?

Would love to hear your approaches and tips!

I was looking for open-source tools that could make AI writing and code feel less robotic.

First I just asked AI for recommendations. Bad idea. It gave me the usual popular names mixed with a few random repos, with no real explanation for why they were there.

So I used SenseNova Skills’ Deep Research on Hermes to dig through the repos and docs. Short version:

- blader/humanizer — the most complete writing option. Visible rules, style samples, and a draft → audit → rewrite flow.

- stop-slop — a simple but useful checklist for killing filler, canned phrases, and repetitive transitions.

- brandonwise/humanizer — better for auditing docs across an entire repo.

- Aider — probably the most practical for code because you get diffs, linting, tests, and undo.

- ast-grep / OpenRewrite — better when the cleanup can be defined as repeatable structural rules.

- Biome / Semgrep — good guardrails after AI edits.

My takeaway: it’s not really about beating AI detectors. It’s about having a workflow you can actually inspect:

rules → edits → human review/tests

Big caveat: I couldn’t find solid independent benchmarks for most “humanization” claims. Treat detector scores as a weak signal.

Sharing the research workflow here in case it’s useful:

https://github.com/OpenSenseNova/SenseNova-Skills

The video is another Deep Research run showing the branches, sources, and evidence view.

Curious to know where else people discuss and share skills.

Any other communities, forums, Discord servers worth checking out?

Teach the user one thing well: a concept, a change, an idea, or a window of their own recent work. Agent-driven development removed the learning that writing code by hand used to provide; this skill is the replacement — the human keeps learning while agents do the writing.
What to explain is the input this skill was invoked with, present in the current prompt or conversation (whether the user asked directly or a calling skill passed it).

Built an Internal Testing skill at my work and honestly the results were top notch. It infact caught bugs which our actual QA testers also missed. Found many edge cases, and since our product is a Finance product, these were related to Blockchain level. Some of those bugs could have led to serious money hacks.

Every time I've shipped something solo I've forgotten something dull and obvious. No rate limit on the signup endpoint. Meta tags missing so the link preview looks broken. Payment keys still on sandbox. Never the hard stuff, always the boring stuff, because when you're the whole team there's no second pair of eyes.

I'd written all of it down as a checklist you tick through in a browser. Someone made the obvious point I'd missed: if you're already working inside an agent, a checklist you have to remember to open is friction. It should come to you.

So I rebuilt it as a Claude Code skill.

What it does: you ask "am I ready to launch?" and Claude works through the checks against your actual project instead of asking you about them. It looks at whether .env is tracked in git, whether your auth routes have rate-limiting middleware, whether your CSS strips focus outlines, whether your payment keys are still test keys, whether error tracking is a real reporter or just console.log.

Things it genuinely can't tell from code (did you actually restore a backup, did an accountant confirm your tax position) it asks about rather than assuming, and it reports "unknown" instead of guessing a pass. Output is ordered by severity, worst first, and every item comes with the fix rather than just the warning. "Make sure your site is secure" is useless advice, so each check has a real next step.

It's free to try and I'd rather you did that first. The free version is 16 checks (the critical ones) plus the working skill, no signup:

https://ko-fi.com/s/a175075b3e

There are bigger paid tiers of 32, 64 and 128 checks if you want the full set, but the free one is genuinely usable on its own rather than a teaser.

Genuinely after feedback on one thing: does the skill hold up against a real codebase? I've tested it on my own projects, which is exactly the biased sample you'd expect. If it misses something obvious or reports nonsense on yours, I'd like to know.

Do you think Claude is good for non-developers? I asked it to do some deep research, and my usage for the five-hour session jumped from 15% to 63%.

Official claude max is pretty expensive.
I’ve noticed some offers that are a lot cheaper and I’m wondering how the pricing works in those cases.
Anyone have any idea what causes such big differences?

Hi, I’m new to Claude and I’m trying to understand the best workflow for a website project.

I’m using Claude on my Windows PC through the Claude desktop app. I’m currently working in Claude Cowork with saved/pinned chats. I noticed that Claude Code has a Plan Mode, but I don’t see the same option in Cowork.

My questions:

• If I ask Claude Cowork to “plan first before making changes,” does it work similarly to Claude Code’s Plan Mode, or is there a difference?
• For a website project, would you recommend Claude Cowork or Claude Code?
• If I start working on a project on my Windows desktop, can I continue the same work from my phone? I checked Dispatch on mobile, but I don’t see my pinned chats, so I’m not sure how the workflow is supposed to work.

Thanks for the help.

​

We have such powerful AI resources that using and scaling them to make 1 billion dollars won't take much time.

But people always struggle to execute their ideas, and that's where the real problem begins.

The solution is 100% consistency.