Skip to content
Frontend Feeds
  • Today
  • Archive
  • Sources
  • Categories
    • The Giants6 Sources
    • Multi Author Blogs18 Sources
    • Top Front-end Bloggers25 Sources
    • More Front-end Bloggers77 Sources
    • Browsers, engines, etc.11 Sources
    • Libraries, Frameworks, etc.12 Sources
    • Company/Startup Blogs12 Sources
    • Developer/Designer News4 Sources
    • YouTube Channels13 Sources
    • Podcasts7 Sources

Today

Front-end, in one read.

The latest from the sources worth following, newest first.

Monday, 16 November 2026

  • CodePenCompany/Startup Blogs4 min read

    Chris’ Corner: Sourcemaps

    Sourcemaps aren’t new, but they’re still fascinating. Neciu Dan recently wrote a good overview article. The CSS and JavaScript we write are likely processed before they become the CSS and JavaScript sent over the internet to a browser. An obvious one is that you might author TypeScript, which is then processed into JavaScript, then bundled, […]

  • DEV CommunityThe Giantsread at source

    Does Claude prompt caching save money? The break-even math

    Originally published at neverpaytwice.pages.dev . Short answer: usually yes, by a lot, but not always. Writing a prompt to the cache costs more than sending it normally (1.25× the input price for the 5-minute cache, 2× for the 1-hour cache). Reading it back costs far less (0.1× on most models, 0.05× on Opus 5.5 and Sonnet 5.5, 0.025× on Fable 5.1 and 5.2). So the 5-minute cache pays off as soon as the cached part is read once . The 1-hour cache needs two reads . A cache that is written and never read makes that part of the prompt 25% or 100% more expensive. Below: the table, three ways it goes wrong, and a script that checks your own logs. How caching is billed When you mark part of a prompt with cache_control , the first request writes it to the cache and later requests that start with exactly the same text read it. Each is a separate line on the bill, priced from the model's input price: What happens Price Write, 5-minute cache (the default) 1.25 × input price Write, 1-hour cache ( "ttl": "1h" ) 2 × input price Read (a cache hit) 0.1 × input price on most models; 0.05× on Claude Opus 5.5 and Sonnet 5.5; 0.025× on Claude Fable 5.1 and 5.2 Every read restarts the cache's lifetime at no extra cost. So requests that share a prefix and start less than 5 minutes apart keep the default cache alive for as long as they keep coming. The break-even point Take one cached prompt section that is written once and then read n times while the cache is alive. Measured in "the price of sending that section once": with caching: write + n × read without caching: n + 1 caching wins when n > (write − 1) ÷ (1 − read) For the 5-minute cache that is n > 0.26 to 0.28 depending on the read price: one read is enough. For the 1-hour cache it is n > 1.03 to 1.11 depending on the read price: two reads . What you save on the cached section, for a few values of n: Cache · read 0 reads 1 read 2 reads 5 reads 20 reads 5-min · 0.1× −25% 32.5% 51.7% 70.8% 84.5% 5-min · 0.05× −25% 35.0% 55.0% 75.0% 89.3% 5-min · 0.025× −25% 36.3% 56.7% 77.1% 91.7% 1-hour · 0.1× −100% −5.0% 26.7% 58.3% 81.0% 1-hour · 0.05× −100% −2.5% 30.0% 62.5% 85.7% 1-hour · 0.025× −100% −1.2% 31.7% 64.6% 88.1% Negative means caching cost more than not caching. These percentages are for the cached part of the prompt only; new input and output tokens cost the same either way. Worked example. A 20,000-token system prompt on Claude Sonnet 5.5 ($2 per million input tokens), used by 10 requests within a few minutes. Without caching: 10 × 20,000 × $2 ÷ 1,000,000 = $0.40 . With the 5-minute cache: one write (20,000 × $2 × 1.25 = $0.05) plus nine reads (9 × 20,000 × $0.10 = $0.018) = $0.068 , 83% less. Three ways caching quietly costs you more The prefix keeps changing. The cache matches the start of the prompt exactly, byte for byte. A timestamp, a request ID or tools listed in a different order near the top means every request writes a new entry and none reads one. In the example above that is ten writes: $0.50 instead of $0.40, 25% more than not caching at all. Requests are further apart than the cache lasts. Requests every 10 minutes never hit a 5-minute cache, so each one pays for a write. Six requests over an hour: 6 × 1.25 = 7.5 "prompt prices" instead of 6. The 1-hour cache fits that pattern: one write and five reads is 2 + 5 × 0.05 = 2.25 on Sonnet 5.5, 62.5% less than not caching. The 1-hour cache for traffic that is already continuous. If requests come less than 5 minutes apart, each read keeps the default cache alive anyway. Paying 2× instead of 1.25× for the write buys nothing. One thing that does not cost you: a prompt shorter than the model's minimum (512 tokens on the current Claude models, up to 4,096 on some older ones) simply isn't cached, with no error and no write charge. You can tell because both cache fields come back as 0. How to see it in your own numbers Every response's usage block has the counts: cache_creation_input_tokens (written), cache_read_input_tokens (read) and input_tokens (neither). If the reads stay at zero across requests that should share a prefix, something at the start of the prompt is changing. A healthy setup reads many tokens for every token it writes. This script adds it up from your logs and compares what you paid with what the same tokens would have cost with no caching. It reads JSON Lines files with a model and a usage block on each line (log response.model and response.usage.to_dict() from the Python SDK), and also Claude Code's own logs in ~/.claude/projects , priced at API rates. It prints numbers only and sends nothing anywhere. ( Download it , or get it with the other scripts on GitHub .) python3 claude_cache_savings.py ~/.claude/projects Requests: 2 Input tokens: 40020 (50% read from cache, 50% written to cache) Reads per written token: 1.0 You paid: $0.0580 Without caching: $0.0860 Caching saved: $0.0280 (32.5%) That sample is two Sonnet 5.5 requests that shared a 20,000-token prefix: one write, one read, the 32.5% from the table. The core of it: WRITE_5M , WRITE_1H = 1.25 , 2.0 def costs ( model , usage , prices = PRICES ) : """(paid, without caching) in USD for one request, or None if the model has no price.""" p = prices . get ( model ) if p is None : return None new_in = usage . get ( "input_tokens" ) or 0 writes = usage . get ( "cache_creation_input_tokens" ) or 0 w1h = ( usage . get ( "cache_creation" ) or { } ) . get ( "ephemeral_1h_input_tokens" ) or 0 w5 = max ( 0 , writes - w1h ) read = usage . get ( "cache_read_input_tokens" ) or 0 out = usage . get ( "output_tokens" ) or 0 paid = ( new_in * p [ "input" ] + w5 * p [ "input" ] * WRITE_5M + w1h * p [ "input" ] * WRITE_1H + read * p [ "cache_read" ] + out * p [ "output" ] ) / 1_000_000 no_cache = ( ( new_in + writes + read ) * p [ "input" ] + out * p [ "output" ] ) / 1_000_000 return paid , no_cache We tested it on 33 usage blocks across 11 models, including 1-hour cache writes: the cost it computes matches NeverPayTwice's own engine every time. It keeps one record per response when Claude Code logs the same response several times, and it lists any model it has no price for instead of counting it as free. It uses standard rates only; the Batch API, US-only inference and fast mode change prices and are not applied. Or let something record it for you NeverPayTwice is a small app we make. Its live meter sits on your own computer between your code and the API ( ANTHROPIC_BASE_URL=http://127.0.0.1:8098/anthropic ) and keeps a receipt for every request with new input, cache writes and cache reads priced separately, so you can see when cache writes are not followed by reads. It never blocks or changes a request, and API keys are never stored. It also flags every time you paid again for a request you had already bought. Works with Anthropic, OpenAI, Google Gemini and compatible APIs. Mac, Windows or Linux, $9 one time. Sources: Anthropic's prompt caching guide (write and read prices, cache lifetime and refresh, minimum lengths) and pricing page , checked November 14, 2026. Prices can change; check the current pages if something doesn't match. Try the demo with sample data , no sign-up, or get NeverPayTwice for $9 .

  • DEV CommunityThe Giantsread at source

    Seamless Head Swap on Flux 2 Klein 9B: Rank 128 and the Upscale Trap

    Head swapping is a narrower task than face swapping: you are replacing the whole head — hair, jawline, neck transition — and the seam problem is proportionally larger. This workflow uses a high-rank LoRA on Flux 2 Klein 9B to make it work. The graph Node Value UNETLoader flux-2-klein-9b.safetensors CLIPLoader qwen_3_8b_fp8mixed.safetensors , type flux2 VAELoader flux2-vae.safetensors LoraLoaderModelOnly bfs_head_v1_flux-klein_9b_step3500_rank128B.safetensors at 1.0 EmptyFlux2LatentImage 1024 × 1024 57 nodes. Rank 128 versus rank 16 Compare this LoRA against the Qwen version in an adjacent release: Qwen: bfs_head_v5_2511_merged_version_rank_16_fp16 — rank 16 Flux Klein: bfs_head_v1_flux-klein_9b_step3500_rank128B — rank 128 Eight times the rank. That is not an accident — it reflects what a head swap needs versus a face swap. A face swap replaces the interior of a face region. A head swap replaces hair, skull shape, jawline, and the neck transition, then has to match the body's proportions and the scene's lighting. That is a much larger transformation, and a low-rank LoRA cannot express it. The trade: rank 128 has more capacity to change the image, including changing things you did not want changed. That is why the workflow includes an upscale stage — it is compensating for detail the high-rank swap disturbed. step3500 in the filename The LoRA was captured at training step 3500. That matters for anyone comparing LoRAs of the same name: a step2000 checkpoint of the same training run will behave differently from step3500 . The filename here is unusually informative — most LoRAs do not tell you which checkpoint they are. The flux2 text encoder qwen_3_8b_fp8mixed with type flux2 . Note the size: 8B , not the 4B or 0.6B used by other Qwen-based pipelines. Flux 2 needs a larger encoder, and using a smaller one will not error — it will just produce weaker prompt adherence. If you are porting this graph to a machine with less memory, do not swap the encoder for a smaller Qwen — swap the whole model family instead. Encoder size is not a free parameter here. Where this breaks Rank 128 changes more than the head. Expect to need masks even when the workflow does not show them. fp8mixed encoder — quantised, so very long prompts degrade more than on a full-precision encoder. 1024×1024 square latent means non-square source images get letterboxed or cropped implicitly. The upscale stage is compensating, not fixing. If the swap disturbed the background, upscaling makes the disturbance sharper, not better. Practical approach Do the swap at 1024, inspect at 1:1, then decide whether to upscale. If the swap introduced changes outside the head region, fix the mask before upscaling — upscaling a damaged image is wasted work. Workflows One graph, published on RunningHub with invite code rh-v1111 : Flux 2 Klein 9B seamless head swap with upscale, master version. Files https://huggingface.co/AI-KSK/ksk-video-187-comfyui-workflows Notes Workflow file only. Model weights are not included; each keeps its own licence. Tutorial export, not a product. Node count and loader values quoted above are read from the published JSON file. Independent AI-KSK release. Not affiliated with Black Forest Labs or RunningHub.

  • DEV CommunityThe Giantsread at source

    FireRed Image Edit 1.0 vs Qwen 2511: Anti-Drift Versus Free-Range Editing, and a Filename With a Space

    Image editors fail in two opposite directions: they either change too little (the edit does not happen) or change too much (the whole image drifts). This release tests FireRed Image Edit 1.0 against Qwen 2511 across five edit types, with separate graphs for the anti-drift and free-range configurations. The five tests Background, lighting, prop, removal, recolour. That list is well-chosen because it ranges from structural (background) to subtle (recolour), and different editors fail differently across that range. The graphs Workflow Nodes Single-image edit, anti-drift 29 Single-image edit, free-range 28 Two-image edit 28 Nearly identical node counts — the difference between anti-drift and free-range is configuration, not structure. That is worth noting: the two modes are one graph with different sampling settings, not two different architectures. The loader stack Node Value UNETLoader FireRed-Image-Edit-1.0_fp8_e4m3fn.safetensors CLIPLoader qwen_2.5_vl_7b_fp8_scaled.safetensors , type qwen_image VAELoader qwen_image_vae.safetensors EmptySD3LatentImage 928 × 1664 LoraLoaderModelOnly Qwen-Image-Lightning-8steps-V2.0 bf16.safetensors at 1.0 The filename has a space in it Qwen-Image-Lightning-8steps-V2.0 bf16.safetensors There is a literal space between V2.0 and bf16 . This is not a transcription artifact — it is the actual filename. Two consequences: Shell and CLI paths break. Any command-line tool that splits on whitespace will fail unless the path is quoted. Download scripts with naive filename handling may save it without the space, and then the workflow's reference no longer matches. If the model fails to load and you are certain it is present, check whether the filename on disk matches exactly, space included. sd3 latent node on a Qwen model EmptySD3LatentImage — the SD3 latent node — used with a Qwen encoder and Qwen VAE. That is not an error; it is a latent-shape node reused across model families. But it means the node name does not tell you which model it belongs to, and anyone filtering nodes by "which model uses this" will get the wrong answer. Anti-drift versus free-range The naming says what each is for: Anti-drift — the edit should be confined. The model is constrained to change only what the instruction names. Good for removal, recolour, and anything where the surrounding image must stay identical. Free-range — the model is allowed to re-interpret the whole image. Good for background replacement and lighting changes, where a confined edit looks pasted. Getting this wrong is the most common source of disappointing results: running a background replacement in anti-drift mode gives a subject floating on an unchanged background. Why eight steps Qwen-Image-Lightning-8steps-V2.0 at full weight. Eight steps is a compromise between four-step speed and the fidelity a careful edit needs. For editing specifically, step count affects how much of the unchanged image survives . Fewer steps means more drift in the untouched regions. Eight is a reasonable floor for edits that must be conservative. Where this breaks The space in the filename. 928 × 1664 is fixed. Source images with other aspects get implicitly cropped or letterboxed. FP8 quantisation on both UNET and encoder compounds detail loss. The anti-drift / free-range distinction is not documented in the files — you have to know which graph is which, and the node counts do not distinguish them. Eight steps is a floor, not a ceiling. For subtle edits, more steps helps. How to use the comparison Run all five edit types through both modes and score on: did the named edit happen, and did anything else change. The second question is the one that separates the modes, and it is the one people forget to check. Workflows Three graphs, published on RunningHub with invite code rh-v1111 : FireRed Image Edit 1.0 single-image edit (anti-drift) FireRed Image Edit 1.0 single-image edit (free-range) FireRed Image Edit 1.0 two-image edit Files https://huggingface.co/AI-KSK/ksk-video-184-comfyui-workflows Notes Workflow files only. Model weights are not included; each keeps its own licence. Tutorial exports, not a product. Node counts and loader values quoted above are read from the published JSON files. Independent AI-KSK release. Not affiliated with the model authors or RunningHub.

  • DEV CommunityThe Giantsread at source

    Property Knowledge Assistants: 3 Admission Checks Before Image API Cost Estimation

    Admit an image generation API request only when its billing units are known, its cost estimate covers the permitted attempts, and the tenant has enough unreserved budget. For a property management assistant answering questions over a private knowledge base, keep this decision separate from the answer itself: generating an illustrative maintenance image should be an explicit action with its own admission check. Short answer: To estimate image generation API model cost before calling, resolve the exact requested configuration against a verified rate schedule, calculate the chargeable quantity or a documented upper bound, and reserve that amount before dispatch. If the billing basis cannot be bounded, return an unavailable estimate and require a separate approval path. An estimate is permission to attempt work, not a promise about the eventual invoice. The operating objective is controlled admission under uncertainty. A smaller displayed number isn't evidence that a request is safe to execute. What makes an image generation API cost estimate safe for admission? Consider a proposed workflow in which a property manager asks the assistant about a maintenance procedure, receives an answer grounded in the private knowledge base, and then requests 2 illustrative images from a text description. The answer and the image action have different acceptance criteria. A generated illustration should not acquire the authority of a retrieved building document merely because both appear in the same conversation. Label it accordingly, and have the image action consume an explicitly approved description rather than automatically forwarding the retrieved documents. Start with scope. The estimate should identify the tenant, selected model configuration, requested image count, billing basis, schedule revision, currency, expiration, and maximum number of attempts. These are proposed fields in an application contract, not claims about a provider's response schema. Preserve the original provider configuration alongside the normalized fields; an adapter that silently substitutes an unsupported size or quality setting can invalidate the estimate while still producing an image that looks acceptable. For this workflow, provider portability means being able to reject an incompatible request clearly and compare supported configurations deliberately, rather than pretending that every model accepts interchangeable controls. The available public service overview does not establish an executable rate schedule for an arbitrary image configuration. Don't infer one from it. Populate the schedule from the applicable, verified commercial terms for the chosen configuration, record where the rate came from, and reject a missing or expired entry. That evidence is required before this design can produce a monetary quote. There is no universal rate in this note. For a documented per-image billing basis, the proposed calculation is requested images multiplied by the applicable rate, with additional dimensions included wherever the actual billing terms require them. For a basis involving quantities that are unknown before execution, return an interval only when there is a defensible bound for every uncertain component. Keep currencies separate. If the evidence cannot support an upper bound, call the estimate unavailable; a guessed maximum is still a guess. Treat estimate drift as an admission signal A useful failure signal is disagreement between the request that was quoted and the request that is about to run. Require dispatch to match the tenant, configuration, quantity, schedule revision, and expiration attached to the reservation. Changing the prompt may also require a new estimate if the documented billing basis depends on its contents. Bind the reservation to the approved request so an adapter cannot quietly turn an estimate for one configuration into authorization for another. Retries need their own allowance. In the example, 2 requested images with 1 permitted retry of the whole request represent up to 4 image attempts (2 images × 2 attempts); that is a proposed reservation policy, not a claim that every failed attempt is billed. Use the actual billing terms to refine the bound, and treat an ambiguous completion as unresolved until usage or reconciliation evidence settles it. Automatically releasing the reservation on a local timeout would let uncertain work disappear from the ledger while another attempt consumes capacity. Pause the retry. Track estimate availability and admission latency as separate SLO indicators from image completion, with targets chosen for the assistant's workflow. Also track rejected configurations, expired quotes, outstanding reservations, and settled charges that exceed their associated bounds. An overrun should trigger investigation of the schedule, request matching, or attempt accounting before increasing tenant limits. The question-answering path can remain available while the optional image action waits for a valid estimate. Capacity planning belongs here too. Bound concurrent image attempts and queued actions independently of monetary reservations: an affordable batch can still exhaust the workers allocated to interactive requests. Use the same proposed two-image request when testing both controls, then increase concurrency deliberately until the configured admission limit rejects further work. Don't describe that exercise as a benchmark. Implement the bounded part of the calculation The following Go example implements only the arithmetic for a verified per-image rate. Amounts use integer billing ticks in one currency, where the schedule defines the value of a tick. A rate of zero can be valid; negative values cannot. The code deliberately rejects overflow rather than wrapping a large reservation into a small one. package admission import "errors" // UnitRate applies only to the exact configuration resolved upstream. type UnitRate struct { Currency string Revision string TicksPerImage int64 } // ReserveTicks bounds attempts; maxAttempts includes the first call. func ReserveTicks ( images , maxAttempts int64 , rate UnitRate ) ( int64 , error ) { if images 0 || maxAttempts 0 { return 0 , errors . New ( "positive images and attempts required" ) } if rate . Currency == "" || rate . Revision == "" || rate . TicksPerImage 0 { return 0 , errors . New ( "verified rate metadata required" ) } const maxInt64 int64 = 1 63 - 1 if images > maxInt64 / maxAttempts { return 0 , errors . New ( "attempt quantity overflow" ) } quantity := images * maxAttempts if rate . TicksPerImage != 0 && quantity > maxInt64 / rate . TicksPerImage { return 0 , errors . New ( "reservation amount overflow" ) } return quantity * rate . TicksPerImage , nil } This function cannot establish that a rate is current, that a configuration is eligible for per-image billing, or that the tenant owns the request. Those checks belong before it. If the applicable billing terms include other components, this calculation is insufficient and the adapter must supply the additional bounded quantities or decline to estimate. After calculation, reserve the amount atomically against the tenant's remaining allowance before putting the action on the dispatch queue. Give each logical action a stable identifier and record individual attempts underneath it. Concurrent workers must not each authorize spending against the same unreserved balance, and a repeated admission request must retrieve the existing reservation rather than create another one. Persist the request binding, calculation inputs, and state transitions so reconciliation doesn't depend on reconstructing them from chat history. This is harder. An application identifier alone does not guarantee that an external service will deduplicate dispatches. Treat external idempotency as a capability that must be verified for the selected operation; if completion is ambiguous and deduplication is unverified, hold the reservation and reconcile before retrying. Set retention and access rules for accounting records without copying private maintenance documents into operational logs. Decide who owns the reservation ledger The buy-versus-build decision should turn on control of admission semantics and the on-call work required to preserve them. The following table describes options to evaluate, not capabilities promised by a particular service. Choice Evidence required before adoption Operational trade-off Managed accounting component Demonstrated tenant isolation, atomic reservations, auditable transitions, and usable export Less ledger implementation work if these requirements are met; migration depends on exported state and semantics Application-owned ledger Concurrency tests, recovery procedures, and an assigned reconciliation owner Direct control over request binding and portability; the platform team owns correctness and recovery Hybrid arrangement A documented authority for each state transition and a tested reconciliation boundary Can retain application admission rules; disagreement between records needs an explicit resolution process Require a recoverable ledger before debating which option is more convenient. For a platform roadmap, a managed component that cannot export unresolved reservations creates a concrete migration constraint; an application-owned implementation without a recovery owner creates a concrete on-call obligation. Neither disappears because the image endpoint is easy to call. Verify admission, then rehearse rollback Before enabling the image action, exercise missing rates, expired schedules, unsupported configuration changes, duplicate admission, concurrent reservations, cancellation, overflow, and an ambiguous completion. Use local fixtures with explicitly synthetic amounts, then validate the deployed adapter against the applicable billing evidence. The two-image example with two maximum attempts must reserve four image units for the supported per-image case; changing the count after admission must invalidate dispatch authorization. Reconcile every completed action against its reservation using the available billing or usage evidence, and record the provenance and timing of that evidence. A response without authoritative charge information should remain pending reconciliation. Distinguish a settled zero charge from a missing charge so monitoring cannot interpret absent data as successful estimation. Roll out with a capped tenant cohort and explicit concurrency limits. Gate expansion on correct request binding, resolved reservation states, and the chosen admission SLO, rather than on the number of images successfully returned. Review unresolved work before the next expansion. For rollback, stop admitting new image actions, retain in-flight reservations, and restore a previously verified adapter and schedule only for compatible requests. A deployment rollback must not erase the accounting state needed to settle attempts already dispatched. Keep the private knowledge-base answer available, explain that the optional illustration is awaiting authorization, and reopen image admission only after request matching and reconciliation checks pass. The acceptance rule is operational: a portable adapter must preserve the meaning of an authorized request, including its attempt bound and unresolved accounting state. A plausible estimate without that preservation is too weak to authorize execution. References AWS Bedrock official overview; service context only, not a configuration-specific image rate schedule: https://aws.amazon.com/bedrock/

  • DEV CommunityThe Giantsread at source

    SkyReels V3 R2V Merged With VACE: Skeleton-Guided Video on a Wan 14B Base

    Skeleton-guided video generation is one of the more reliable control signals available: a pose sequence is unambiguous in a way that text is not. This workflow merges SkyReels V3's R2V capability with VACE's control path on a Wan 14B base. The graph Node Value UNETLoader wan-14B_vace_skyreels_v3_R2V_e4m3fn_v1.safetensors , dtype fp8_e4m3fn CLIPLoader umt5_xxl_fp8_e4m3fn_scaled.safetensors , type wan VAELoader Wan2.1_VAE.pth 66 nodes. The merged checkpoint The UNET filename describes exactly what it is: wan-14B — the Wan 14B base vace — VACE control path included skyreels_v3 — SkyReels V3 R2V behaviour R2V — reference-to-video e4m3fn — FP8 quantisation, e4m3 v1 — first merged version A merged checkpoint like this bundles behaviour that would otherwise be separate LoRAs or adapters. The advantage is that you load one file instead of three and there is no ordering problem between them. The disadvantage is that you cannot tune the individual contributions — you get the merge as designed. The VAE is .pth , not .safetensors Wan2.1_VAE.pth — a PyTorch pickle rather than safetensors. This matters for two reasons. First, .pth files can execute arbitrary code on load, so they should only come from a source you trust. Second, tooling that expects safetensors will not find it. If you have been collecting safetensors only, this workflow will fail at the VAE load, not at the model load. The umt5-xxl text encoder umt5_xxl_fp8_e4m3fn_scaled with type wan . UMT5-XXL is a large multilingual encoder — this is why Wan-family models handle Chinese prompts better than CLIP-based pipelines. The scaled suffix means the weights have been rescaled for FP8, which is different from simply quantising them. Why skeleton guidance works A pose skeleton supplies: joint positions, limb angles, and a temporal progression. There is no ambiguity in the way there is with "the person raises their arm" — the arm either goes where the skeleton says or the render is visibly wrong. The failure modes are correspondingly specific: Skeleton and body proportions disagree — the model produces a body that has to stretch to hit the joints Occlusion is unconstrained — a skeleton does not say which limb is in front Hand and face detail is absent — skeletons stop at the wrist Those three are why skeleton control produces strong overall motion and weak detail. Where this breaks .pth VAE — tooling incompatibility and a trust question. Merged checkpoint means no component-level tuning. Hands. Skeletons stop at the wrist; the model has to invent fingers from nothing. Occlusion ordering. With two limbs crossing, the skeleton does not say which is in front and the model guesses. FP8 quantisation on both UNET and encoder — detail loss compounds across two quantised stages. Practical approach Start with a single-subject, single-limb action where occlusion is not an issue. Confirm the skeleton aligns with the rendered body. Only then try two-limb interactions, and expect to need a mask or a second pass for hands. Workflows One graph, published on RunningHub with invite code rh-v1111 : VACE + SkyReels V3 R2V merged skeleton-guided video. Files https://huggingface.co/AI-KSK/ksk-video-186-comfyui-workflows Notes Workflow file only. Model weights are not included; each keeps its own licence. Tutorial export, not a product. Node count and loader values quoted above are read from the published JSON file. Independent AI-KSK release. Not affiliated with the model authors or RunningHub.

  • CSS-TricksThe Giantsread at source

    Staggering Scroll-Driven Animations with animation-range-start

    Imagine a CSS karaoke machine that displays a ball bouncing on text that incrementally highlights, based on progress through via speech recognition and running that kind of animation as a single predictable, holistic effect driven by one progress value. Staggering Scroll-Driven Animations with animation-range-start originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

  • Level AccessCompany/Startup Blogs13 min read

    Accessibility Testing Tools: A Guide for Enterprise Teams

    Accessibility testing tools like scanners, browser extensions, and monitoring platforms find barriers at scale. Pair them with manual testing to catch what automation The post Accessibility Testing Tools: A Guide for Enterprise Teams appeared first on Level Access .

  • Flavio CopesMore Front-end Bloggersread at source

    AI is eroding my coding skills, and I don't care

    63% of developers in a Syntax survey say their coding skills are diminishing. Mine are too. Here is why it doesn't worry me, and which skills I still keep.

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Make a custom deck of playing cards with your family and friend's faces

    Comments

  • Hacker News Front PageThe Giantsread at source

    Nvidia Was in Trouble Before the Jensen Huang Mess

  • Frontend Masters BlogMore Front-end Bloggers11 min read

    Browsers To Try If You’re Being Forced Off Arc

    Arc will sunset on December 22, 2026. Here's some personal notes from trying a variety of a new crop of alternatives. There's some good ones!

  • David BushellMore Front-end Bloggers2 min read

    Visited links are purple

    A few weeks ago Kev Quirk asked: Do you use :visited on links? — and I said to myself: No! I don’t use visited links… but why don’t I use visited links? TL;DR: I’ve gone and styled visited links, and they’re purple. Blue and purple I did a cursory five minutes of research and found Wikipedia still […]

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Mac's Notes, Reminders and Photos never reach Android, so I built them

    Comments

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Nobody blocks a keyboard – Rooted Android as a physical USB Deck

    Comments

  • Hacker News Front PageThe Giantsread at source

    Whistleblower accuses Pentagon over Iran strike on US base that killed 6

  • Hacker News Front PageThe Giantsread at source

    The Active Directory Era Is Finally Over

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: SketchProbe – decode Apache DataSketches binaries, runs via WebAssembly

    Comments

  • Hacker News Front PageThe Giantsread at source

    What is w2rt6byl5nf1opmc-a.com?

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Localhost2137 – Emulate external APIs locally, without API keys

    Comments

  • Hacker News Front PageThe Giantsread at source

    Many of Amazon’s Black Friday and Cyber Monday “Deals” Offered No Savings

  • Jeffrey Zeldman PresentsMore Front-end Bloggers3 min read

    Standout Designs for the Web

    Andy Clarke’s Standout Designs for the Web ships Wednesday and is now available for pre-order. I had the honor of writing the Foreword, reprinted here: Foreword I first met British art director, writer, and illustrator Andy Clarke at the SXSW Interactive festival in Austin, Texas. At the time, SXSW was the number one destination for […] The post Standout Designs for the Web appeared first on Jeffrey Zeldman Presents .

  • HeyDesignerDeveloper/Designer Newsread at source

    Continuing a style isn't the same as starting one

    Working with designers, Design engineering has a handoff problem, The CSS caret-* properties and custom caret accessibility.

  • SitePointThe Giantsread at source

    Build Live Video Chat With WebRTC: From First Call to Production Debugging

    null Continue reading Build Live Video Chat With WebRTC: From First Call to Production Debugging on SitePoint .

  • SitePointThe Giantsread at source

    What Is the Best UI design Tool? 8 Tools Compared by the Job They Do (2026)

    null Continue reading What Is the Best UI design Tool? 8 Tools Compared by the Job They Do (2026) on SitePoint .

  • Speckyboy Design MagazineDeveloper/Designer News3 min read

    The Most Profitable Service Your Agency Isn’t Selling

    Stop giving away hosting and maintenance. Productize care plans into recurring revenue, improve retention, and turn free favors into a profitable agency service. The post The Most Profitable Service Your Agency Isn’t Selling appeared first on Speckyboy Design Magazine .

  • Net NinjaYouTube ChannelsVideoWatch on YouTube

    "Anti-Slop" Designs with Impeccable (a Crash Course) #4 - Live Mode

  • Darek KayMore Front-end Bloggersread at source

    #0199

    A mural of a man wearing a white periwig and sunglasses with rainbow beams. A big sign on the wall reads 'London 1759'. A shadow casts a line from the sunglasses to a person walking on the street wearing sunglasses.

  • SitePointThe Giantsread at source

    Markdown to PDF in 2026: No-Install Methods and the Rendering Problems Nobody Warns You About

    null Continue reading Markdown to PDF in 2026: No-Install Methods and the Rendering Problems Nobody Warns You About on SitePoint .

  • Brad FrostTop Front-end Bloggers4 min read

    Foundations matter more than ever

    Oh boy! Our biggest sale of the year starts today; you can master design systems, join a vibrant community, and save over 33% on all of our courses . That's right, it's that time of the year where we bust out our Black Friday tap-dancing shoes. We know that tap dancing can be…

  • Sara SoueidanTop Front-end Bloggers27 min read

    The CSS caret-* properties and custom caret accessibility

    What do you usually think about when you think about focus indicators? Probably outlines? Maybe borders and background color changes, too? That’s what I would normally think about. When we talk about focus indicators, the discussion usually revolves around outlines, borders, and…

Sunday, 15 November 2026

  • AbduzeedoMulti Author Blogsread at source

    BOND Unveils Aleph Farms Brand Identity

    BOND builds the Aleph Farms brand identity from a single flipped letter for cultivated meat: the ancient aleph, turned over, becomes an ox. BOND calls it turning steak on its head. Cultivated meat is ...

  • AbduzeedoMulti Author Blogsread at source

    How Studio Freight Reimagined Thesis Brand Identity

    Studio Freight builds the Thesis brand identity from zine culture: an asterisk mark, dot-grid Harber type, and electric lime. The system starts from a position, not a logo. Thesis builds brands on Bit...

  • David BushellMore Front-end Bloggers4 min read

    RSS Club #010: Chatbots

    This is an RSS-only post, thank you for subscribing :) My RSS-only posts have a permalink for those who prefer reading from my website. That link is hidden and unindexed. URLs can be linked to but in the spirit of “RSS Club” I’d prefer if my RSS-only posts were only linked to from other RSS-only […]

  • AbduzeedoMulti Author Blogsread at source

    Inside the Best of the Week: Backlit Ink, Waxed Kraft, and SMK

    Our curated best of the week roundup covers Pentagram's backlit print, Studio Hi Ho's waxed butter wraps, and eTypes' SMK overhaul. Material honesty kept surfacing across our favorite studio releases ...

  • Jeffrey Zeldman PresentsMore Front-end Bloggers5 min read

    Thanks for nothing, Apple Logic Pro

    Apple Logic Pro breaks the customer mental model and its own brain with ill-considered “Unified Browser” reminiscent of everything terrible. Prepare for a deluge of ugly metaphors. The post Thanks for nothing, Apple Logic Pro appeared first on Jeffrey Zeldman Presents .

  • Flavio CopesMore Front-end Bloggersread at source

    What are your agents doing all night?

    People say their agents run 24/7. Here is what they run at night, what the skeptics answer, which jobs deserve a schedule, and how I check my own scheduled agents.

  • SitePointThe Giantsread at source

    How AI Image-to-Image and Image-to-Video Tools Work, and How to Build a Reliable Workflow

    null Continue reading How AI Image-to-Image and Image-to-Video Tools Work, and How to Build a Reliable Workflow on SitePoint .

  • Chris HawkesYouTube ChannelsVideoWatch on YouTube

    I Can Build Almost Anything Now. It Doesn't Feel the Same.

Saturday, 14 November 2026

  • AbduzeedoMulti Author Blogsread at source

    Inventure: Nordic Venture Capital Branding by Bedow

    Stockholm studio Bedow builds its branding for Nordic venture firm Inventure around a two-part wordmark and 30-degree slanted headlines. Halfway through the INVENTURE logotype, the bottom edge stops d...

  • Jens Oliver MeiertTop Front-end Bloggersread at source

    Two Underappreciated Observations About Our Exposure to Other Humans

    On hidden dynamics and quiet autonomy.

  • AbduzeedoMulti Author Blogsread at source

    Julia Brand Identity: Inside Hey Studio's Ribbon Wordmark

    Hey Studio formed Julia's wordmark from real ribbon and photographed it, so the Julia brand identity keeps every fold, crease and shadow. The idea starts with a gesture, not a typeface. Tying a bow me...

  • AbduzeedoMulti Author Blogsread at source

    Graphic Design: Toronto Symphony Orchestra by Underline Studio

    Underline Studio anchors its graphic design for the Toronto Symphony Orchestra around an echoing serif S and color-coded season print. T and O don’t budge in the new Toronto Symphony Orchestra monogra...

  • AbduzeedoMulti Author Blogsread at source

    Ray Gun Magazine: The Design That Broke Every Rule

    Ray Gun magazine launched in November 1992 and tore up the rulebook of editorial design, with David Carson turning type into image. The premiere issue sets the tone on the cover alone. The masthead re...

  • AbduzeedoMulti Author Blogsread at source

    Branding: Philadelphia Museum of Art Brand Identity by Gretel

    Gretel rebuilt the Philadelphia Museum of Art brand identity around a revived griffin, custom Fairmount Serif and Philly street type. The badge does the heavy lifting. A black roundel holds a white gr...

  • HTML All The ThingsPodcastsAudioListen

    The Problem With Putting All Your Tech in One Basket

    Microsoft 365 went down, leaving users struggling to access emails, files, and communication tools. But the bigger question is: are we putting too many eggs in one basket? In this edition of the Web News, Matt and Mike discuss the risks of relying on centralized software…

  • SitePointThe Giantsread at source

    Securing FastAPI Applications: JWT Authentication and Rate Limiting with Redis

    null Continue reading Securing FastAPI Applications: JWT Authentication and Rate Limiting with Redis on SitePoint .

  • SitePointThe Giantsread at source

    How to Build a Unified Lead Tracking Pipeline for Web Forms and Phone Calls

    null Continue reading How to Build a Unified Lead Tracking Pipeline for Web Forms and Phone Calls on SitePoint .

  • Flavio CopesMore Front-end Bloggersread at source

    How to use Fable as the orchestrator and Opus as the executor in Claude Code

    Run Claude Code with Fable 5.2 planning and reviewing while Opus 5.5 sub-agents do the work: the setting, the prompt, and what a real job cost me.

  • SitePointThe Giantsread at source

    Logging AI Prompts and Responses in Java Without Leaking Sensitive Data

    null Continue reading Logging AI Prompts and Responses in Java Without Leaking Sensitive Data on SitePoint .

  • SitePointThe Giantsread at source

    Your SSL certificates can now last 200 days at most: The real risk isn’t renewal

    SSL certificates now last 200 days at most, dropping to 47 by 2029. See why automated renewals still fail quietly and how to monitor certificates before they expire. Continue reading Your SSL certificates can now last 200 days at most: The real risk isn’t renewal on SitePoint .

  • Swizec TellerMore Front-end Bloggersread at source

    Software has no value

    Software is never the goal, what software can help you do is the goal.

Friday, 13 November 2026

  • Flavio CopesMore Front-end Bloggersread at source

    How to audit your CLAUDE.md with /doctor prompt-audit

    Claude Code's /doctor prompt-audit finds stale facts, contradictions and dated wording in CLAUDE.md, AGENTS.md and your skills. I ran it on this site's repo.

  • Engineering at MetaCompany/Startup Blogs5 min read

    Cuttlefish on Mac: Running Android’s Virtual Device Framework Natively on Apple Silicon

    How Meta's Reality Labs brought Cuttlefish and its QEMU backend to macOS and Apple silicon. [...] Read More... The post Cuttlefish on Mac: Running Android’s Virtual Device Framework Natively on Apple Silicon appeared first on Engineering at Meta .

  • Dave RupertTop Front-end Bloggersread at source

    Conventional Commit rules everything around me

    There’s a community standard out there called Conventional Commit for structured git-commit messages. If you don’t know about it already, it recommends a strict type(scope?): description format for describing a code change in a repo. A normal git commit history might look like this: > git log --oneline 9d30ff6 fix typo 3062496 oops d0b38ad shit b5f8df7 redesign site That’s all well and good, but lacks a bit of structure and detail for a big project with lots of contributors. That’s where Conventional Commit comes in. Instead of a git-commit message like add login page , it might look like this: feat: add user login endpoint Or you can “scope” it to a particular section of your application: feat(auth): add user login endpoint There’s even a ! flag to signal a breaking change to your coworkers: feat!: remove all authentication API endpoints The predefined conventional commit types cover most types of changes: fix: , feat: , chore: , docs: , style: , refactor: , perf: , test: , build: , and ci: . I find these cover most situations but I’m also a bad boy and like to break rules, so I’ll throw in custom types like wip: , a11y: , hotfix: , or an rm: (as a treat) when I feel it adds clarity to the work. But why would anyone voluntarily conform to a standard like this? My answer is… a feeling . Look at our git-log history now: > git log --oneline 9d30ff6 fix(input): restore focus state on input 3062496 style(checkbox): update tokens to tokens v2 d0b38ad chore: update dependencies via dependabot b5f8df7 feat(auth): add user login endpoint ... In a noisy repo that’s increasingly getting noisier (thanks, robots) anywhere you can add predictability is a net-positive. The cumulative effect over time is that you have a highly-scannable, uniform history of what’s happening in your project. Conventional Commit can even help with code review. A style: fix that adds dozens of npm packages should be a signal that you need to break up the work. Types might also inform if you route all a11y: commits to the local expert for code review. And a refactor! breaking change should signal coworkers to be extra-cautious in review and may trigger other process-oriented workflows like broadcasting the upcoming breaking change to anyone in the blast radius. And because it’s a community standard, like the Custom Element Manifest , you can build tooling around it like commitlint . As its name implies, commitlint is a linter that gates all commit messages from your entire team to ensure they abide in the type(scope): description format. I personally tend to avoid adding extra tooling to enforce simple conventions, but I might change my mind on this because the benefits start compounding. If my commits were all similarly formatted, I could also automate our entire changelog and semantic versioning bumps for releases. fix: = PATCH feat: = MINOR any!: = MAJOR Of course, Conventional Commit and Semver itself aren’t perfect but it adds a degree of predictability about the impact of a change from the description alone. Abiding in the Conventional Commit format is a small micro-adjustment to my process, but it has potential to positively impact the entire project and I like those sorts of zero-dollar improvements. Extending Conventional Commit beyond commits One place you’ll also want to extend conventional commit to is pull request titles . Not technically a git-commit message, but if you squash and merge commits the PR title tends to become the commit message by default. Preferring or enforcing conventional commit in pull request titles helps preserve our pristine commit history. If you’re doing pull request titles, why not use them for issue titles too: #123 > bug(input): required focus indcator missing #122 > feat(checkbox): update tokens to v2 #112 > chore: update dependencies from depdendabot #106 > feat(input): make input more engaging There’s harmony when the issue and the solution are matching. Having the type in the issue title sets a clear deliverable; a bug: needs a fix: to resolve it. Consider these duplicate issues for the same bug: #189 > 4.2.7 Focus Visible [bug] [components] [severity:HIGH] #210 > bug(input): focus indicator is missing Which one would get picked up first? I’d argue that even with labels like [bug] and [severity:HIGH] that the second one would be easier to fix because it gives the developer almost all the information they need to fix the issue. It makes the issue a little more actionable and that’s what you want. If every issue is an investigation, nothing gets done. Triaging issues takes cognitive bandwidth . Labels are great at grouping and providing queryable views, but when scanning a list of issues pairing both the tag and the title to determine the ask adds an extra cognitive tax. I’m projecting here, but uniform data in your PRs and issue queues could also allow you to collect stats on which components or areas of your application are the most buggy and expensive to maintain. It can tell you who’s getting saddled with all the bugs or which issue filer is adding too much feature debt. And it can help your team quantify your recurring maintenance tasks that might be hiding because it gets rolled into other work. That might be valuable to an organization. Unconventional usage of Conventional Commit Now let’s extend beyond the practical. I’m finding the Conventional Commit format to be so useful, I’ve started rolling them out to a lot of different places (surprise, coworkers!). One example is our folder full of random scripts/ in the monorepo. What was a randomized list of dozens of scripts and tests… scripts/ ├── docs-tokens.mjs ├── playwright-cli.mjs ├── storybook-compat-table.mjs ├── style-dictionary.mjs ├── sync-fluent-fluent-custom-elements-manifest.mjs ├── validate-themes.mjs └── visual-review-harness.mjs Can become an organized paradise of co-located responsibility: scripts/ ├── build/ │ └── themes-style-dictionary.mjs ├── docs/ │ ├── storybook-generate-compat-table.mjs │ ├── tokens-generate-table.mjs │ └── sync-fluent-custom-elements-manifest.mjs └── test/ ├── playwright-cli.mjs └── playwright-visual-review-harness.mjs └── themes-validator.mjs I’ve found those Conventional Commit types tend to map well to areas of responsibility for repo-level scripts. Manage docs, tests, build tasks, and so on all fit under the Conventional Commit umbrella and it adds some much needed organization to the junk drawer of copy-pasta and generated helper scripts. And if your scripts/ folder is following the Conventional Commit format… why not roll that out to your scripts in package.json : { "scripts": { "docs:generate": "node ./scripts/docs/generate-storybook-compat-table.mjs && node ./scripts/docs/generate-storybook-tokens-table.mjs", "build:themes": "node ./scripts/build/themes-style-dictionary.mjs", "test:themes": "node ./scripts/test/themes-validator.mjs" } } Built-in npm features like pre* and post* hooks mess up our perfect naming system a bit. A prebuild:themes task reads fine but predocs:generate is a bit marble-mouthy. But that’s an eye-twitching discrepancy I’m willing to accept to abide in what npm gives me for free. Then… if you’ve added Conventional Commit to your scripts/ and your "scripts" and are living that agentic coding life, why not apply the same organization principle to your skills/ folder? skills/ ├── build/ │ ├── themes/SKILL.md ├── docs/ │ ├── component-jsdoc/SKILL.md │ ├── storybook/SKILL.md │ └── technical-writing/SKILL.md └── test/ ├── playwright-tests/SKILL.md ├── visual-tests/SKILL.md └── writing-tests/SKILL.md This looks great… it falls apart in the real world. Skills installed from the internet don’t abide in this format. Having some skills nested and others not creates a feeling of unease, so a flatter folder structure for skills is probably better. That said, it’s not uncommon to need a skill to inform your model about your repo-level scripts and those are places you can still maintain parity. skills/ ├── build-themes/SKILL.md ├── docs-storybook/SKILL.md ├── docs-components/SKILL.md ├── docs-technical-writing/SKILL.md ├── grill-me/SKILL.md ├── i-have-adhd/SKILL.md ├── test-playwright/SKILL.md ├── test-visual-review/SKILL.md └── test-writing/SKILL.md While applying Conventional Commit to your skills/ folder is a bit impractical, one area I can confirm it does help is organizing your agent chats. Fire off a handful of agents and it can get confusing about which one is doing what task, even with their autogenerated chat label. I’ve found it super helpful to ask your bot to rename its chat using the Conventional Commit format. Try it out and bask in the uniform list of tasks. To get this to work consistently in the GitHub Copilot app, I had to modify my session prompt in Sessions > App instructions: At the start of every new chat, before answering my first request, call `rename_session` using `type(scope): description`. Do this even for non-coding chats. Rename only once unless I ask otherwise. I’m not sure how it works in your preferred agent manager, but I assume you could write a skill or put it in your AGENTS.md , but I’d have a conversation with your coworkers first before codifying your obsessive-compulsions in the project repo. Join me in my obsession You might have read all this and said, “This is a man who –in a world of chaos– is looking to over-manage a small thing like title text so that he can feel in control of his own life!” and to that I’d say… Probably. I like to think I’ve just hit the point in my life where I don’t want to spend an single brain cell thinking about how I should format title text or name a file. I wasn’t this passionate about Conventional Commit a year ago, I think I got radicalized. Generative AI almost certainly plays a big part where every robot names files and fixes different every time. That’s built-in to its dice-roll mechanic. Knowing there’s a chaos agent in the mix, I feel a need to find low-hanging fruit for consistency and (for right now) this feels pretty good to me.

  • CSS-TricksThe Giantsread at source

    10 Big Ol’ 2027 Black Friday Deals

    A big ol' roundup of Black Friday deals on front-end courses from the best independent publishers and educators in the business. 10 Big Ol’ 2027 Black Friday Deals originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

  • AdactioTop Front-end Bloggersread at source

    The speakers at #FFconf have such excellent taste!

  • Darek KayMore Front-end Bloggersread at source

    #0198

    An ICM photo that looks like a painting. Golden leaves under a pergola are lighted by the sun.

  • Jeffrey Zeldman PresentsMore Front-end Bloggers1 min read

    Diggs This

    RZA of Wu-Tang Clan has invested in AYO Music Group, the music copyright company co-founded by Tracklib’s Pär Almqvist and clearance veteran Deborah Mannis-Gardner. AYO helps rightsholders get more out of their catalogues. Bobby Digital is in the building. Pär (AKA Peyo) Almqvist is a magical creative being and my Swedish brother. If past lives […] The post Diggs This appeared first on Jeffrey Zeldman Presents .

  • Net NinjaYouTube ChannelsVideoWatch on YouTube

    "Anti-Slop" Designs with Impeccable (a Crash Course) #3 - Full Page Redesign

See everything from the last 30 days →

Articles belong to their publishers. This site only collects what their feeds provide.

Updated 16 November 2026 at 16:53