Drill: Redesign the slop: take a generic SaaS landing page (gradient hero, 3 feature cards, emoji icons) and redesign it to avoid every anti-slop rule in claude-design. Target: same content, 10x less generic.
Interpretation: Built as Cadence, a project-management SaaS — the domain with the highest slop potential. Warm editorial aesthetic (stone canvas + single burnt-sienna accent #c2410c), real product-UI fragment in the hero instead of a gradient blob, honest metrics with failure context, opinionated voice that takes positions. An 8-row audit panel documents each slop-to-fix transformation.
Cadence is a planning and tracking tool for product teams who've outgrown Trello and out-tolerated Jira. Cycles, not checklists. Roadmaps you can actually read. No AI button that summarizes your standup into nothing.
No credit card. 14 days on the Team plan, then drops to Free — not a paywall.
You don't have a ticket problem. You have a "where did this go and who's waiting on it" problem. Here's what breaks, and how Cadence is built around the breakage.
A task gets "done" in a Slack thread, a Linear issue stays open for three weeks, and the roadmap still shows it as Q3. Nobody knows what's actually shipping.
A Gantt chart with 40 bars stretching to December is a wish list with gridlines. By week three it's stale and nobody re-reads it.
Status is scattered across Jira, Notion, Slack, and a Loom nobody watched. The answer to "are we on track" is always "let me check and get back to you."
Four things that matter, done deliberately. No feature graveyard, no settings page with 90 toggles.
Link a PR to a cycle item and the item's status follows the PR. Merged = done. Draft = in progress. Closed-unmerged = parked, with a reason.
github.com · gitlab.com · bitbucketTwo-week cycles, a "next" column, and a "later" parking lot. Stakeholders see a timeline that matches reality, not a December fantasy.
auto-rolls every cycle closeThe cycle view IS the status report. Blockers surface in red. No one writes a Friday update email because the page already answers it.
shareable link · no login to viewBring your Jira, Linear, or Asana projects in. Cadence maps them to cycles and tells you which 40% of tickets have had no activity in 60 days.
jira · linear · asana · csvNo animated counters, no "10,000+ teams." Three things we can actually defend.
We killed our weekly status meeting in the second cycle. The cycle page already said everything the meeting was going to say — and it said it without someone having to write a deck.
Per active user, billed monthly. Active = someone who closed at least one item this cycle. Your finance team will notice.
A short list of features we chose not to build. If you need these, we're the wrong tool — and that's fine to say out loud.
AI standup summaries. If your standup can be summarized by a model, you didn't need the standup. Fix the meeting, don't automate the suffering.
Gantt charts. We tried. They lie. Cycle-scoped roadmaps are honest because they can only hold what fits in two weeks.
Story points. They're a unit nobody agrees on and everyone games. We track items shipped and time-to-close — both measurable.
Custom fields playground. Six field types, on purpose. If your process needs 40 custom fields, the process is the problem.
The generic SaaS landing this page replaced had every pattern below. Each row shows the slop pattern, the specific move that replaced it, and the anti-slop rule it serves. This panel is the drill artifact; the page above is the result.