Bashid Effendi @bashide

What is an agent harness? rubriclabs.com/blog/what-is-a…

Lost my phone at the office and spent 30 minutes turning the place over. Find My was disabled by MDM. Out of ideas, I asked Claude how I could find it. It suggested tracking the Bluetooth signal strength, then wrote me a meter in about a minute. I walked around watching the number climb. Found it. Apparently you can just make the tool you need now. Code: github.com/ben-z/findphone

saas hero section designs from last month made with fable 5

keyboard_arrow_left Previous keyboard_arrow_right Next

Respect to Fable 5, but this is a different league.

keyboard_arrow_left Previous keyboard_arrow_right Next

@imrenagi @dhanyindraswara @grok Izin nimbrung, di video yang mana sih bang, aku ke youtube belum nemu😄

Asem, udah terlanjur langganan yang 4 juta sebulan padahal. Hidup ini kalo ngga ketiban sial dari presiden sendiri, ya sama presiden kontol satu itu.

Anthropic @AnthropicAI

4 months ago

The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of

12K 25K 87K 93.5M 23K

@davidsunarna Percuma juga punya free time. Langganan yang Max 5 sekali ngasih prompt aja udah kena limit🤣

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.

Claude @claudeai

5 months ago

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.

5K 14K 103K 57.7M 21K

GitHub acaba de solucionar el mayor problema del vibe coding. Acaban de lanzar Spec Kit y en días ya tiene +95K estrellas. ¿La idea? En vez de tirar prompts vagos y rezar para que el agente no rompa tu proyecto… Spec Kit obliga a la IA a crear una especificación estructurada ANTES de tocar código. La IA primero entiende lo que quieres construir, pregunta lo que falta, organiza el proyecto y después empieza a programar. Eso significa menos tiempo arreglando errores absurdos, menos código inconsistente y resultados mucho más predecibles cuando trabajas con agentes. El flujo es simple: /constitution → reglas y estándares /specify → qué quieres construir /clarify → dudas antes de empezar /plan → arquitectura y stack /tasks → tareas ordenadas /implement → ejecución Compatible con Claude Code, Cursor, Copilot, Codex, Gemini CLI y +25 agentes. 95K estrellas. 8K forks. Open source. Publicado por GitHub. Repositorio 👇

@rayestu Iyes, justru kalo email lebih reliable, bisa ambil data e-statement, e-wallet, ecommerce, subscription dll. Kalo yg wasap itu kebanyakan berbayar juga API-nya. Belum tau kalo telegram.

@rayestu Wah sip, masih terjangkau ya ternyata, dari kemarin mau build tapi takut kemahalan. Udah vibecoding buat platformnya, tinggal connect-in ke wasap😁

keyboard_arrow_left Previous keyboard_arrow_right Next

superpowers is still the simplest way to level up any project you're running in Claude setup takes under 5 minutes. gets you to plan and map projects properly (code or non-code) GPT image 2 generated a breakdown of the article below save it and send it to your agent

Shann³ @shannholmberg

7 months ago

x.com/i/article/2037…

11 77 742 559K 2K

@MichLieben ads

Best GitHub repos for Claude Code that will 10x your next project in 2026 1. Claude Mem github.com/thedotmack/cla… Persistent memory across sessions — stop re-teaching Claude your codebase 2. UI UX Pro Max github.com/czlonkowski/n8… 50+ styles, 161 color palettes, 99 UX guidelines — Claude stops building ugly UIs 3. n8n-MCP github.com/czlonkowski/n8… Connect Claude Code to 400+ n8n integrations via MCP 4. LightRAG github.com/hkuds/lightrag… Graph + vector RAG — lets Claude understand large codebases structurally 5. Everything Claude Code github.com/affaan-m/every… Skills, instincts, security scanning, multi-language coverage — full agent harness 6. Awesome Claude Code github.com/sickn33/antigr… Community bible — curated skills, hooks, slash commands, orchestrators 7. Superpowers github.com/obra/superpowe… Forces structured thinking before writing a single line of code 8. Claude Code Ultimate Guide github.com/FlorianBruniau… 23K+ lines of docs, 219 templates, 271 quizzes — beginner to power user 9. Antigravity Awesome Skills github.com/sickn33/antigr… 1,200+ ready-to-use skills — one of the largest collections 10. Claude Agent Blueprints github.com/danielrosehill… 75+ agent workspace templates beyond coding 11. VoiceMode MCP github.com/mbailey/voicem… Natural voice conversations with Claude Code via Whisper + Kokoro 12. Awesome Claude Plugins github.com/ComposioHQ/awe… 9,000+ repos indexed with adoption metrics — find what people actually install Bookmark this before your next build.

Sebagai seorang yang sangat puas dengan fitur “Claude for Excel”, saya bertanya pada Claude tiga hari lalu, kapan “Claude for Word” rilis, eh hari ini beneran rilis🤣

Claude @claudeai

7 months ago

Claude for Word is now in beta. Draft, edit, and revise documents directly from the sidebar. Claude preserves your formatting, and edits appear as tracked changes. Available on Team and Enterprise plans.

1K 2K 31K 12.5M 11K

@rayestu Di aku kerasa banget sih nambahnya, semenjak upgrade ke max 5x hampir gapernah kena limit, biasanya yg pro 4-5 kali prompt di claude for excel udah kena limit😅

gaes, aku sama temenku mulai jualan jam vintage di ig. untuk awal-awal masih banyak jam kecil yang mungkin cocok untuk cewek, but next bakal ada jam cowok juga. pls check us out! instagram.com/tempus.collect… (psst, i can give you a deal if you're interested)

keyboard_arrow_left Previous keyboard_arrow_right Next

btw di Canva skrg bisa bikin aplikasi. Coba deh reply mau dibikini aplikasi apa. Nanti gua coba bikinin misal: - aplikasi masukin berat badan, tinggi badan, terus keluar BMI - catat keuangan pribadi - alat hitung workout, dsb

@axzrael @hane3y x.com/bashide/status…