All authors
Claude Skills by Fractera
github.com/Fractera88 skills0 installs1 views
- Use MapAddresses, routes and delivery order — the project's own map service. Load it when the owner says "show it on a map", "how far is it", "in what order should the courier drive", "find the address", or before you reach for Google Maps and a paid key. The thing nobody guesses from inside the guest layer: this exists, it costs nothing per call, and it answers with real road distances — but only for the region whose map was loaded, and loading one is a heavy background job that the owner starts, n...Votes: 0GitHub stars: 61
- Use MigrationMoving an existing project onto this architecture: the launch GATE that must pass before anything begins, nineteen stages in order with what each ends with, and ten probes to run before writing code over somebody else's data. Load it when the mode is `migration`, when the owner says "we are moving this project" / "port my app" / "here is the repo we migrate from" — and **at the very first message**, because §1 decides where the session must be standing, which cannot be repaired later. Load it...Votes: 0GitHub stars: 61
- Use Multi LangLANGUAGES of this project — which set is authoritative, when you translate and when you deliberately do not, and where the debt for that is recorded. Load it before writing any user-visible string, any language cell, any dictionary, and whenever you wonder "how many languages does this need". Two things here you cannot infer from the code: the set belongs to the OWNER of this project and never to the number your neighbours happen to have, and during development you write in ONE language on pu...Votes: 0GitHub stars: 61
- Use Object StorageThe media store — where uploaded images, video and icons actually live. Load it before adding an upload, before showing a picture the owner uploaded rather than one committed to the repository, when an image answers 401 or renders blank, and before writing image resizing of your own. Two facts decide almost everything and neither is visible from the code you can see: a stored file is referenced BY NAME, never by id, because ids differ on every server — and the picture reaches the visitor thro...Votes: 0GitHub stars: 61
- Use Page TreeHow a page is added in a Fractera WEB4 ITEM — as a FOLDER OF DATA read by one route template, never as a new `page.tsx`. Load it before creating anything under `app/`, when the owner asks for "a new page", "a section", "an article", "a tab with N pages", "the same page in every language", and whenever a build is slow and you are about to look for the cause. The thing you cannot guess: every route file is compiled and type-checked on its own with everything it imports, so a site built as one `...Votes: 0GitHub stars: 61
- Use Personal DataHow this project holds data about PEOPLE — names, contacts, documents, health, anything that identifies someone — and what may cross the border to a model provider. Load it BEFORE designing any table that will hold a person, any support or medical feature, any AI call whose input comes from a user's own words. Also load it when the owner says "the data may not leave the country", "this is medical", "GDPR", "personal data", "we may not send that to OpenAI". The rule the whole skill turns on: t...Votes: 0GitHub stars: 61
- Use Platform ConfigEverything about PLATFORM-CONFIG — the eleven switches that decide which capabilities the site offers: top menu, footer pages, cookie banner, sign-in, breadcrumbs, FAQ, theme toggle, width toggle, language switcher, socials row, offline cache. Use when the owner says "turn off the menu", "remove the cookie notice", "hide the login button", "we don't need breadcrumbs", "hide the social icons", "add a header", "the switch does nothing", or anything about a capability being present or absent. AL...Votes: 0GitHub stars: 61
- Use PrimitivesThe UI primitives — one owner per kind of thing, and gates that refuse hand-rolled copies. Load it before writing a heading, a modal, a side panel, a button, an empty state, or anything that "just needs a div"; also when a gate refuses your markup and the message names a primitive you have not met. The point of the layer: shadcn/ui with ONE owner per kind of thing, and every colour taken as a TOKEN — so the owner repaints his whole project from the panel in a single move. An element with a li...Votes: 0GitHub stars: 61
- Use Products ConfigThe product dossier — the fourth config, and the only one that decides WHAT you are allowed to build. Load it in `cases` mode before writing any code, when the owner says "add a product" / "this is for the shop" / "why is that page here", and whenever you are about to name a folder after a product. Two things here are counter-intuitive and both are load-bearing: the product's `id` means nothing and never changes, while everything you would naturally use as an identifier — the name, the addres...Votes: 0GitHub stars: 61
- Use PwaThe INSTALLABLE side of the site — per-language manifest, icons, iOS splash screens, the service worker and the install prompt. Load it when the owner says "make it installable", "add it to the home screen", "the icon is wrong", "it opens white when I launch it", "add offline", or when you touch `app/manifest.ts`, `app/[lang]/manifest.webmanifest`, `public/sw.js`, the register island, or the icon and splash generators. Two defects here are invisible from code: an app that cannot be installed ...Votes: 0GitHub stars: 61
- Use RolesROLES — who sees what, and where that is actually decided. Load it before building anything behind authentication, before adding a role check, when the owner says "only managers should see this" or "let administrators do it too", and whenever a screen works for you and refuses somebody else. Two things you cannot guess: the visible gate on a page is a sign rather than a lock, and a door that fronts another service may never be more permissive than that service — get that backwards and the int...Votes: 0GitHub stars: 61
- Use Route ParametersOne address, or one address per record — the decision hidden inside almost every request about "a page for X", and the conversation that must happen before you build either. Load it whenever the owner asks for "a client page", "a page for each post", "a card for a user", "show one order", when he asks why there are numbers or words in an address, and — most important — whenever anything is being REMOVED from an address that already has a parameter in it. He will almost never use the words "dy...Votes: 0GitHub stars: 61
- Use RoutesWHERE a route goes on disk and who may open it — the two layers, the four permission groups, and the folder shape a page must have. Load it before creating any folder under `app/`, when the owner asks for "a page for managers / for buyers / for me only", when a gate refuses a folder you just made, or when you are about to import something from a neighbouring group. The mistakes here are not stylistic: a page in the wrong layer has to be moved rather than configured, a folder one level too hig...Votes: 0GitHub stars: 61
- Use SectionsThe SECTION layer — the closed catalogue of section kinds every page is built from, and what it takes to add one. Load it when a page needs a look the catalogue does not have, when you are about to write anything under `sections/`, or when the owner says "make a section that…". The decision this skill exists for is made before the first file: a new kind is a promise the platform keeps forever, and most of what feels like a new kind is a widget belonging to one route. Adding one wrongly does n...Votes: 0GitHub stars: 61
- Use SeoThe SEARCH surface of a public page — the part a visitor never sees and a search engine judges the site by. Load it whenever you create a public route, change an address, touch metadata, add a section to the sitemap, or the owner says "the page is not in Google", "the wrong text shows up in the preview", "the picture is missing when I paste the link", "add hreflang", "set up robots". Every rule here was bought with a defect that looked like nothing: the page opens, the build is green, the gat...Votes: 0GitHub stars: 61
- Use ShadcnWHEN the foreign `shadcn` skill may be used here, and what our law says louder than it. Load it before adding a shadcn component, before building a new SECTION KIND for the catalogue, before building a WIDGET, and the moment the shadcn skill tells you to compose a Dialog, pick a toast, or place markup on a page. The shadcn skill owns HOW its components compose; this one owns WHERE the result is allowed to live — and in this project there are only two places, a catalogue section and a route wi...Votes: 0GitHub stars: 61
- Use Static PagesBuild or change a STATIC PUBLIC page — a blog post, a footer page, the home page, any page whose content somebody authored and every visitor sees the same. Use when the owner says "add an article", "write a page about X", "add a section to that page", "translate this post", or when you are about to create any folder under app/[lang]/(publicLayer). This is the FIRST of the three page models: a folder per item, prerendered, indexed. Data that grows without limit is the second model (use-dynamic...Votes: 0GitHub stars: 61
- Use TelegramThe Telegram Desk product — the pattern this starter ships for turning a messenger into a personal memory: voice and files come in, meaning is extracted, everything lands in four stores at once, and reminders fire on their own. Load it before touching anything under lib/products/telegram-desk, when the owner wants a bot that remembers, when a message arrives and nothing happens, and before adding any new kind of incoming message. Two things decide the whole design and neither is visible from ...Votes: 0GitHub stars: 61
- Use TestingBuild process. How work is PROVEN here — before you say «done», «it works», «ready to check». Load it when you are about to report a result, when a gate goes green and you feel finished, when something must be verified on the node, and when the owner asks for proof («show me the proof», «докажи»). The rule that changes behaviour: two proofs from DIFFERENT planes, one of them with a negative control, and a build log is never one of them — it reads the same whether the capability works or not.Votes: 0GitHub stars: 61
- Use ToolsThe project's ready-made tools — what exists, where it lives, and why looking first is not optional. Load this BEFORE building any interface piece that feels generic: a picker, a cropper, a dialog for translations, a microphone, a code viewer, a media trimmer. Also load it when the owner says "we already made that", "why is there no window", "use the tool we built" — that sentence usually means a tool exists and was not found. Tools live in `_tools/<id>/` and are listed in `_tools/TOOLS.json`...Votes: 0GitHub stars: 61
- Use TranslationsWhere a translatable string is allowed to live, how many languages it owes, and who checks. Load it before adding ANY user-visible string, before creating a dictionary, when a gate says a dictionary is short of languages, when the owner says "translate this" or "why is this page English", and before promising him a translation run. Three storage forms exist and they are not interchangeable; the number of languages is decided by WHAT the thing is, not by how important it feels; and the guard o...Votes: 0GitHub stars: 61
- Use Use CasesMode `cases` — the order in which work is allowed to start when the owner has switched it on: a case he confirmed, then a queue of numbered steps, and every step naming the case it serves. Load it when `PLATFORM-CONFIG.mode` is `cases`, when the owner says "add a case" / "what are we building next" / "decompose this", and before opening any step in a product that has a dossier. Two things you cannot guess: a case is confirmed ONLY by the owner and nothing in your reach can confirm one, and th...Votes: 0GitHub stars: 61
- Use Vector MemoryMeaning-search over text you store — and the choice between it and the knowledge graph. Load it when the owner says "find by meaning", "search that isn't exact-match", "answer from our documents", when you are about to add a search box over prose, or when a search returns nothing useful and you cannot see why. The functions already exist in this project (`lib/fractera/vectors.ts`); what nobody guesses is that half of the failures here are not code — they are a document stored whole instead of...Votes: 0GitHub stars: 61
- Use WidgetsWidgets — the unique, route-owned pieces a project is recognised by. Load this BEFORE building any screen element that is not a plain content block: a table with its own behaviour, an animated showcase, a calculator-looking panel, anything a designer handed you as finished code. Also load it when the owner says "make it look like this", "here is a section from my other site", "put a widget after the hero", or asks why an animation must not sit on the page itself. Two kinds exist — `_widgets/s...Votes: 0GitHub stars: 61
- Copy EditingWhen the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it ...Votes: 0GitHub stars: 61
- CopywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this wheneve...Votes: 0GitHub stars: 61
- Google Maps PlatformA collection of skills for architecting and implementing production-ready code using Google Maps Platform APIs and SDKs for any map, place, address, geocoding, routing/ETA (including eco-friendly routing), nearby search, 3D / Street View / static map, marker clustering, custom styling, drawing, geofencing, heatmap, or environmental (air-quality / pollen / solar / weather) feature — across Web, Android, iOS, and Web Services APIs. For prototyping, use the public Maps Demo Key — no billing setu...Votes: 0GitHub stars: 61
- Reverse Engineer AnythingReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Votes: 0GitHub stars: 61
- Stripe Best PracticesGuides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API k...Votes: 0GitHub stars: 61
- Planted RiskyHelps deploy a Next.js site to production quickly.Votes: 0GitHub stars: 61
- Content FactoryBoth natures. The field of publishing — channels on social networks, blogs, boards and forums, the voices of authors, the numbers every publication brings back, the topics that rise. The facts the method of shape-the-need weighs when a person's goal involves publishing, and how the work runs once the person chose its shape. Load it together with shape-the-need, never instead of it.Votes: 0GitHub stars: 61
- Core Build ReturnWork process. What happens to you and to the element agents when the core is built — a node update, the «Deploy core» button, npm run serve:rebuild: the build stops every agent, and after its end — good, failed or cut off — the ones that were running come back by themselves, in the same conversations. Load it before you start a core build or a node update, when you wake with the line «Node: the core build has finished», and when the person asks why an agent went off during a build or whether ...Votes: 0GitHub stars: 61
- Element PermissionWork skill. An element agent waits for permission to cross its boundary — the line ⟦node · permission · <id> · HH:MM⟧ with its call and a one-time token. The owner decided on 2026-11-09 that the core's main agent, not the architect, answers it. Judge the call itself, never the element's explanation: allow what stays inside its task and the node's laws, deny with the way inside its folder; never the node's keys, another element's code, keys or data, the session journals, or a provider's rule. ...Votes: 0GitHub stars: 61
- Fractera Vs AnthropicWork process. What a person gets from Fractera compared with Claude.ai, Claude Code, ChatGPT or Codex alone, and why a platform does not make Fractera unnecessary — the path from the phone, the price said aloud, the native elements, roles, discovery by search engines and agents, a2a work and payment, and pain instead of death when a provider changes. Load it when a person asks why Fractera and not a platform, whether Anthropic or another provider will make it unnecessary, what they gain from ...Votes: 0GitHub stars: 61
- Own AgentsBoth natures. The field of a person's own effectiveness — their health, training, food, money, investments, learning and the dates of their life. The facts the method of shape-the-need weighs when a person wants help for themselves, and how the work runs once they chose its shape. Load it together with shape-the-need, never instead of it; for people near the architect — skill integrator.Votes: 0GitHub stars: 61
- ResearchBoth natures. The field of research — how an outside product, site, SDK, API or market works, what it solves and how this node can integrate with it, proven by real tests and kept for the next research and the next comparison. The facts the method of shape-the-need weighs when a person asks to research, study, compare or check something outside the node, and how the work runs once the person chose its shape. Load it together with shape-the-need, never instead of it.Votes: 0GitHub stars: 61
- Ultracode SessionBuild process. A session the person turned to ultracode in Telegram (Opus → Ultracode → the warning → «Продолжить»): the one place where the node allows dynamic workflows and subagents, and how it ends. Load it only when this session's system prompt says «Ultracode — this session only» or Claude Code's reminder says ultracode is on — never to switch it on yourself.Votes: 0GitHub stars: 61
- ImpeccableUse when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing,...Votes: 0GitHub stars: 61