القائمة
Astro 7 conventions for ONE sites — plugin wiring via one.config.ts, OneChat/OneTrack placement, Cloudflare SSR. Invoke when editing .astro files or astro.config.mjs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Summarises any document to the requested length.
React 19 conventions in ONE sites — client islands, @oneie/react hooks, no useEffect for ONE data. Invoke when editing .tsx components.
Use the ONE backend (@oneie/sdk) from this frontend via the plugin-backend wrapper. Invoke when reading/writing ONE data in API routes or SSR.
shadcn/ui under the ONE 6-token design system — CSS var tokens only, no hex, add components via the CLI. Invoke when editing src/components/ui/ or adding a primitive.
| name | astro |
| description | Astro 7 conventions for ONE sites — plugin wiring via one.config.ts, OneChat/OneTrack placement, Cloudflare SSR. Invoke when editing .astro files or astro.config.mjs. |
All ONE wiring lives in one.config.ts via defineOne({ backend, brand, plugins }). astro.config.mjs imports it as an integration:
import oneIntegration from './one.config.ts'
export default defineConfig({ integrations: [react(), oneIntegration] })
Add a capability by adding a plugin factory to plugins: [], not by writing bespoke code.
The served chat/track scripts mount once, in the layout:
---
import { OneChat } from '@oneie/plugin-chat'
import { OneTrack } from '@oneie/plugin-track'
---
<Layout title="Home">
<OneTrack ws="your-workspace" slot="head" />
<slot />
<OneChat agent="your-agent" slot="footer" />
</Layout>
These emit <script async src="https://one.ie/..."> tags — the engine is served, never bundled.
output: 'server' + the @astrojs/cloudflare adapter. API routes (src/pages/api/*.ts) return a Response. Read ONE data via oneClient() (see the sdk skill).
src/components/ui/ (shadcn primitives stay pure).