Development

Curated trending across GitHub repos and the Hugging Face Hub (models, datasets, spaces) - filtered, clustered, and labeled by momentum with a one-line why-notable per pick.

Generate and send a digest on a configurable topic, optionally pulling RSS/Atom feeds as an input source alongside web + X signal

Generate a small app or tool and deploy it live to Vercel via API

Use when implementing, modifying, or reviewing Android authentication, cryptography, sensitive data handling, or Google Play Billing flows.

WHAT: Explains a codebase, a folder, a feature, a command or a pull request to someone who knows nothing about it, as a PR Lens canvas whose walkthrough builds the picture one part at a time. WHEN: /eli5 <thing>, or asked to explain code simply, for a beginner, a new hire, a non-engineer, or 'like I'm five'. KEYWORDS: eli5, explain like I'm five, explain simply, beginner, onboarding, walkthrough, diagram, PR Lens

Read Google Search Console via CLI — search queries, pages, CTR, position, indexing, sitemaps. TRIGGERS: "search console", "GSC", "what are we ranking for", "search queries", "organic traffic", "impressions", "clicks", "CTR", "average position", "keyword", "is this page indexed", "index coverage", "URL inspection", "sitemap", "SEO performance", "search performance", "brand vs non-brand"

Read Google Analytics 4 via CLI — traffic, acquisition, pages, conversions, realtime. TRIGGERS: "google analytics", "GA4", "analytics report", "how much traffic", "how many visitors", "sessions", "active users", "pageviews", "traffic sources", "acquisition channels", "top pages", "landing pages", "conversion events", "key events", "realtime users", "who is on the site now", "GA4 property", "GA4 dimension", "GA4 metric"

Use when you need to know what depends on something, what a change would break, where a new file belongs, how a request reaches a given component, or who calls a function, in a repository that Knossos has scanned. Answers come from a static graph with file and line evidence instead of from reading the source tree. Also covers recording durable architectural facts for later sessions.

Use when you need to know what depends on something, what a change would break, where a new file belongs, how a request reaches a given component, or who calls a function, in a repository that Knossos has scanned. Answers come from a static graph with file and line evidence instead of from reading the source tree. Also covers recording durable architectural facts for later sessions.

The [agent orientation plugin](../guides/agent-plugin.md) installs two things that do different jobs. The [session brief](session-brief.md) tells a session what this repository looks like at the moment it starts. The skill, `skills/knossos/SKILL.md`, tells it which questions to bring back to the graph for the rest of that session, and which to answer the ordinary way. Nothing invokes the skill by name. Claude Code loads a skill when its description matches the question in front of it, so what...

Control an authorized local Android phone or show its real-time read-only video beside the current local Codex task on macOS. Use for phone app tasks and Android UI checks.

This path builds Linkly with an AI agent. You give the agent one prompt per chapter; it writes the workers, and you check the result. The goal here is to build a working link shortener service while demonstrating iii's efficiency when building systems agentically, along with its 4 core properties which we call CODE: - Composability - Observability - Discoverability - Extensibility We'll present them a bit out of order but hopefully this mnemonic helps you remember what iii is all about.

This path builds Linkly with an AI agent. You give the agent one prompt per chapter; it writes the workers, and you check the result. The goal here is to build a working link shortener service while demonstrating iii's efficiency when building systems agentically, along with its 4 core properties which we call CODE: - Composability - Observability - Discoverability - Extensibility We'll present them a bit out of order but hopefully this mnemonic helps you remember what iii is all about.

engine: workers: configuration: {} containers: state: worker: package://api.workers.iii.dev/state version: "0.22.2" config_name: state api: worker: path://./workers/api start_after: [state] scripts: run: pnpm start ``` Registry packages require an explicit version. `path://` workers use `scripts.run` from the Compose file or `scripts.start` from their `iii.worker.yaml` manifest. Start a project and keep its daemon in the foreground: ```bash iii compose build --file worker-compose.yaml iii com...

api_key: ${ANTHROPIC_API_KEY} ``` </Warning>

<!-- generated by iii-skill-render. DO NOT EDIT (changes here are overwritten on the next render). Edit docs/next/understanding-iii/compose.mdx. -->

`iii-stream` is for **real-time data transmission**: pushing data to a client the moment it changes, like a live feed of clicks for a dashboard. A stream is bidirectional (subscribers can send messages back as well as receive them), but here you only need to broadcast clicks outward. You'll move the live-broadcast concern into its own `click-streamer` worker so the `link` worker stays focused on links.

Linkly's links live in `state`, which you set to in-memory back in Chapter 1. Restart the engine and everything is gone. In this chapter you add a `database` worker (SQLite) that holds the durable record of links and a timestamped row for every click on a short code. `state` stays in the picture as a fast read cache in front of the database. <Info> `state` can also persist on its own (`store_method: file_based` with a `file_path`). This chapter uses a dedicated `database` worker instead, whic...

This tutorial builds **Linkly**, a link shortener, one worker at a time. You start with a single function that turns `/s/abc` into a redirect, and finish with a multi-tenant link platform that has durable execution, storage, analytics, a live click stream, bulk imports, and a browser worker on the same bus. Each chapter adds one capability by adding a worker to your existing system. The point is not the link shortener itself, but the pattern: a real system on iii is a set of small workers tha...

Observability in iii isn't something you bolt onto each service. Every cross-worker call already flows through the engine, so the engine can trace and log the whole system end to end. In this chapter you open the console to see that, then, if you want, read the same data directly from the engine.

iii-worker-manager: host: 127.0.0.1 port: 49134 iii-worker-manager#browser: host: 127.0.0.1 port: 3110 rbac: auth_function_id: auth::browser expose_functions: - match("link::create") - match("link::request_delete") - match("stream::*") ``` Restart the project so Compose can materialize the changed engine configuration: ```bash iii compose --up --namespace linkly --file worker-compose.yaml ``` `expose_functions` is an allowlist of which functions a browser session can call. `auth_function_id` ...

engine: workers: {} containers: http: worker: package://api.workers.iii.dev/http version: "0.21.3" config_name: http state: worker: package://api.workers.iii.dev/state version: "0.22.2" config_name: state config_override: adapter: name: kv config: store_method: in_memory ``` The `engine:` section makes this Compose invocation own the engine. Project workers belong only under `containers:`. `state` uses an in-memory store by default, so every restart starts clean. That's what we want for this ...

value: queue_configs: clicks: type: standard max_retries: 5 concurrency: 5 adapter: name: builtin ``` <Note> Queue names are references to the queue and do not place any restrictions on what can be put into a given queue. </Note> You already wrote `link::record_click` in Chapter 3, where `http::redirect` triggers it directly. Nothing about that function needs to change to make it queuable. You only change how it's triggered with a `TriggerAction`. **First import `TriggerAction`** into `link/s...

Where a stream is for a live trickle of events, a **channel** is for **moving a large amount of data at once**: a direct streaming pipe between two endpoints, rather than one request and response. Channels are bidirectional (each end has both a reader and a writer), but here you'll stream in one direction, uploading a CSV of links. You'll give this its own `bulk-importer` worker so the `link` worker stays focused on single links.