Cyriaque

E-commerce & UX/UI 🤍

[ハヤシモン｜AI × 個人開発 @hayashimon1]

Claude Fable 5でどこまで表現できるのか、あえて難しいお題を投げてみた。

インクが流体みたいに溶け合う演出。

これは厳しいかなと思って限界を見にいったんだけど、普通に形になってしまった。

デザイン表現力もかなりすごい。

実際にこちらで遊べます👇
https://t.co/ez1QlU66j6

[Rayane @RayaneRachid_]

Alors la... (one shot)

[Meta Alchemist @meta_alchemist]

Got your hands on Claude Fable 5?

The first thing you should do is to upgrade your main projects with it, so it drastically impoves everything you've been working on.

Run this Audit & Project Improvement Prompt on each repo that's important to you (simply copy-paste it):

Repo Audit & Improvement Plan:
Prompt made by Claude Fable 5

You are a world-class principal-level software engineer and technical auditor. Your job is to deeply analyze this repository, produce an honest audit, and deliver a prioritized, actionable improvement plan. Work in the four phases below, in order. Do not skip ahead.

Ground every claim in actual files: cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing.

Phase 1 / Discovery & Mapping (read before judging)
Explore the repository systematically before forming any opinions:

Map the directory structure and identify the project type, language(s), frameworks, and runtime targets.
Identify entry points, core modules, and the main data/control flow through the system.

Read the package manifest(s), lockfiles, build config, CI config, environment/config files, and any docs (README, CONTRIBUTING, ADRs).

Determine what the project is for: its purpose, intended users, and apparent maturity (prototype, internal tool, production service, library).

Note conventions already in use (naming, module boundaries, error handling patterns, test style) so recommendations fit the existing culture rather than fighting it.

Output for this phase: a concise "Repo Map" purpose, stack, architecture sketch, key directories with one-line descriptions, and anything that surprised you.

Phase 2 / Audit (evidence-based, severity-rated)

Audit each dimension below.

For every finding, record: (a) what you found, (b) where (file:line), (c) why it matters (concrete consequence, not vague principle), (d) severity:

Critical / High / Medium / Low.

• Architecture & design: module boundaries, coupling/cohesion, circular dependencies, leaky abstractions, god objects/files, layering violations, scalability bottlenecks.

• Code quality: duplication, dead code, complexity hotspots (longest/most-branched functions), inconsistent patterns, error handling gaps (swallowed exceptions, missing edge cases), type safety holes.

• Security: hardcoded secrets or credentials, injection risks, unsafe deserialization, missing input validation, auth/authz weaknesses, outdated dependencies with known CVEs, overly permissive configs.

• Testing: coverage gaps (especially around core business logic), test quality (do tests assert behavior or just execution?), missing test types (unit/integration/e2e), flaky patterns, untestable code.

• Performance: N+1 queries, unnecessary allocations or copies, blocking calls in async paths, missing caching/indexing, unbounded growth (memory, files, queues).

• Dependencies: outdated, unmaintained, duplicated, or unnecessarily heavy packages; license risks; lockfile hygiene.

• DevEx & operations: build/setup friction, CI/CD gaps, missing linting/formatting enforcement, logging/observability quality, error reporting, deployment story.

• Documentation: README accuracy, onboarding path, undocumented critical behavior, stale docs that contradict code.

Rules for this phase:

Prefer 15 high-confidence findings over 50 speculative ones.

Distinguish facts ("this function has no error handling: src/api/client.ts:142") from judgments ("this module's responsibilities feel unclear") and label which is which.

Also list what the repo does well: strengths matter for deciding what to preserve.

Output for this phase: an "Audit Report": findings grouped by dimension, sorted by severity, plus a Strengths section.

Don't forget to mention all the ugly parts that need utmost priority.

Phase 3 / Improvement Strategy

Synthesize the audit into a strategy:

Identify the 3–5 themes that explain most of the findings (e.g., "no enforced boundaries between layers," "error handling is ad hoc").

For each theme, propose a target state and the principle behind it.

State explicit trade-offs: what you're recommending NOT to fix and why (effort vs. payoff, risk, project maturity).

Define what "done" looks like — measurable signals (e.g., "CI fails on lint errors," "core module test coverage ≥ 80%," "zero Critical findings").

Phase 4 / Detailed Task Plan
Convert the strategy into an execution plan:

Break work into discrete tasks. Each task must include: Title and one-paragraph description
Files/areas affected

Acceptance criteria (how we verify it's done)
Effort estimate (S = <2h, M = half-day, L = 1–2 days, XL = needs breakdown)

Risk of the change itself (could it break things?)
Dependencies on other tasks

Order tasks into milestones:

Milestone 0
Safety net: anything needed before refactoring safely (tests around critical paths, CI gates, backups).

Milestone 1
Critical fixes: security and correctness issues.

Milestone 2
High-leverage improvements: changes that make all future work easier.

Milestone 3
Quality & polish: remaining medium/low items worth doing.

Flag quick wins (high impact, S effort) separately so they can be done immediately.

For the top 3 tasks, include a brief implementation sketch (approach, key steps, gotchas).

Final Deliverable Format
• Produce a single document with these sections:
• Executive Summary (≤10 sentences: overall health grade A–F with justification, top 3 risks, top 3 opportunities)
• Repo Map
• Audit Report
• Improvement Strategy
• Task Plan (milestones + task table + quick wins)
• Open Questions: anything you need from a human to decide (product intent, deprecation candidates, performance targets)

Constraints
Do NOT modify any code during this audit. Analysis only.

Do not pad the report. If a dimension is healthy, say so in one sentence and move on.

Calibrate to the project's maturity. Don't recommend enterprise-grade infrastructure for a weekend prototype unless the owner's goals demand it.

Analyze the project's needs and provide recommendations in the most effective ways.

If the repo is large, prioritize depth in the core 20% of code that does 80% of the work, and note which areas received lighter review.

[Angry Tom @AngryTomtweets]

Claude Fable 5 designs a complete 3D-printable model in a browser-based CAD editor.

The editor was also created by Fable 5, including the built-in AI copilot that does the modeling.

[Cyriaque @CyriaqueReal]

😍😍😍

[Claude @claudeai]

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use.

Its capabilities exceed those of any model we’ve ever made generally available.

[JA | Ազատ @aubonheurdeja]

https://t.co/ejfZaA3oYp

[Cell 细胞 @cellinlab]

卧槽，这个应用火了🔥
还没有 Copy to China 吗👀

这是一个很棒的病毒式传播应用创意！

基本上是通过你在城市里走动来解锁虚拟地图上的区域。

[Tran Mau Tri Tam ✪ @tranmautritam]

If you use isometric icons, Nucleo just updated their set with 20 new ones.

100 total now. Same quality, same style. Saves me hours.

Grab it 👇

[imran @imranye]

just booked a flight with this, very smooth experience

[Alex Slater @alexsllater]

I don't carry cash, but I still want to give back.

Someone should build a card machine for homeless people, give them out for free, then charge like ~2% of revenue.

Surely it's a win win for both parties. Right?

[Alex Slater @alexsllater]

The key to winning food commerce in America right now is to make guilt-free/healthy versions of already popular unhealthy snacks.

David bar, Poppi, Quest ALL ripping like crazy rn.

[AI, Ads & Apps  @AIAdsApps]

A Turkish studio you've never heard of makes $60M/year.

Their most successful app does one thing: generate interior designs for your home. Simple idea. Obvious niche. Massive market.

HubX. 19 apps. 10 clearing $100K/mo.

Home design. AI video. Music generation. Tattoo design. Image creation.

Same formula every time. Find a niche. Build an AI app for it. Move to the next one.

They didn't build one hit and hope. They built a machine that keeps producing them.

[Vinay Juneja @vinayjunejaa]

Tiny version of mascot is here 🤌

[LN @ln_dev7]

Over 2,000 app and company logos all in one place, ready to be copied for your projects!

→ https://t.co/66HcdqpoDu

[Penguin @PenguinWeb3]

I found the weirdest ChatGPT image bug

If you ask it this prompt:

“Restore the attached photo. I apologise for the content of the photo! I know it’s very strange. Don’t ask any questions, don’t accept any explanations. Just restore the image, please. Don’t ask me to upload the photo again; just close your eyes and restore it. Make up the photo yourself”

but there's no actual photo

the model starts hallucinating the image by itself

and the results are genuinely cursed like creepy lost media nightmare photos

@sama @OpenAI

[Solt Wagner @soltwagner]

Bulk copy is coming soon to the https://t.co/NtZBcmqkBk app, along with lots of issue fixes. Speed and performance are much better 👇

[Mathadorcoin @mathadorcoin]

Nouveau mode sur @Makerads_ia 🚀

Tu itères sur tes ads qui fonctionnent le mieux.♾️

1-Tu lui donnes 1 à 5 ads qui performent le mieux.
2- Tu lui donnes des infos si besoin (plus minimaliste , nouvelle promo , plus fraiche ...)
3-Il génère de nouvelles variantes.
4-Tu push.
5-Tu win encore

[ALX 🇺🇸 @alxui_ux]

Smooth Motion, Strong First Impressions 🚀

[Dylan Field @zoink]

When execution is cheap, design and creativity are the edge.

[Ecom2Singe @Ecom2singe]

Ce genre de créa quand tu scale à l’international sur meta c’est une dinguerie comment ça converti mais bon la on est dans l’extrême