plocks.dev valid
plocks
A cross-platform React Native UI library — 131 components, 24 charts,
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:59:32.978Z. Cached copy · Source on plocks.dev
# plocks
> A cross-platform React Native UI library — 131 components, 24 charts,
> and 48 hooks that render natively on iOS and Android and as real DOM on the web,
> from one themeable component model.
This index lists plocks documentation pages formatted for LLMs.
Each link points to a standalone Markdown file under the /llms path; any docs URL
with `.md` appended (https://plocks.dev/ui/Button.md) serves the same file.
Whole-library files:
- https://plocks.dev/llms-small.txt (~180k tokens) — every component, chart and hook: imports, own props, one example each. Loads the whole API at once.
- https://plocks.dev/llms-full.txt (~445k tokens) — every page in full, nothing truncated. Larger than most context windows; suited to search and embedding.
Agent skills for Claude Code, Cursor and others: https://github.com/platform-blocks/skills (`npx skills add https://github.com/platform-blocks/skills --skill plocks-setup`)
Install: `npm install @plocks/ui` — separate packages, installed alongside it: `@plocks/brands`, `@plocks/carousel`, `@plocks/charts`, `@plocks/code`, `@plocks/dates`, `@plocks/emoji-picker`, `@plocks/media`, `@plocks/qrcode`, `@plocks/spotlight`. A component page's Import line names the package it comes from.
Version: generated from the `main` branch — `@plocks/ui` 0.2.0, `@plocks/brands` 0.2.0, `@plocks/carousel` 0.2.0, `@plocks/charts` 0.2.0, `@plocks/code` 0.2.0, `@plocks/dates` 0.2.0, `@plocks/emoji-picker` 0.2.0, `@plocks/media` 0.2.0, `@plocks/qrcode` 0.2.0, `@plocks/spotlight` 0.2.0. The branch can be ahead of the latest npm release; if an API here is missing from your installed version, check the changelog: https://github.com/platform-blocks/plocks/tree/main/changelog
Website: https://plocks.dev • GitHub: https://github.com/platform-blocks/plocks • npm: https://www.npmjs.com/package/@plocks/ui
**Conventions**
- Import from the package root: `import { Button, Row, useToast } from '@plocks/ui'`. Some components live in their own package — `@plocks/dates`, `@plocks/charts`, `@plocks/code`, `@plocks/media`, `@plocks/carousel`, `@plocks/spotlight`, `@plocks/brands`, `@plocks/qrcode`, `@plocks/emoji-picker` — installed alongside `@plocks/ui`; each page's Import line names the package.
- Wrap the app once in `<PlocksProvider>` (theme, color scheme, overlays, i18n). `useToast()` and `useDialog()` render through `<ToastProvider>` / `<DialogProvider>` — mount those inside it before calling them. Theming: https://plocks.dev/llms/guides/theming.md
- Lay out with `Block` in place of `View`, `Row` / `Column` for flex stacks (`gap`, `align`, `justify`, `wrap`), and `Grid` + `GridItem` for columns. `Row` and `Column` are documented on the Flex page.
- Most components take the shared style props — spacing (`m`, `p`, `mx`, `py`, …), sizing (`w`, `h`, `fullWidth`, …), `radius`, `shadow` — form inputs share the field props (`label`, `description`, `error`, `helperText`, `required`, …) and charts the chart props. Component pages list their o
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| cubby-ui.dev | Cubby UI | documentation Developer tools Design | US | 45 | ✓ | ✓ | |
| designrevision.com | DesignRevision | documentation Developer tools Design +1 | — | 57 | ✓ | ✓ | |
| tamagui.dev | Tamagui Complete Documentation | documentation Developer tools | — | 55 | ✓ | ✓ | |
| welcome-ui.com | Welcome UI | documentation Developer tools | — | 51 | ✓ | ||
| gluestack.io | gluestack UI | documentation Developer tools Open source projects | US | 45 | ✓ | ✓ | |
| reactbits.dev | React Bits | interface Developer tools Design | — | 56 | ✓ | ||
| rubyui.com | RubyUI | documentation Developer tools Design | — | 50 | ✓ | ✓ | |
| shadcn-cssinjs.com | shadcn-cssinjs | documentation Developer tools Documentation and reference | US | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=plocks.dev · GET /v1/domain/plocks.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage plocks.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for plocks.dev:
1. POST https://agentwebmap.com/v1/sites/plocks.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://plocks.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/plocks.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/plocks.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.