القائمة
Defines which repos each Hora app agent is permitted to read and write. NON-NEGOTIABLE — set by the repo owner; applies to every agent in every session.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate ALL Hora-family app icons AND brand-mark wide cards (Android launcher + notification, iOS, web, Play feature graphic, web OG/social image, GitHub repo social preview) from the shared Baloo Chettan 2 wordmark engine in hora-core. Use when creating or refining any Hora app's icons or brand marks, on any surface.
Use for a fast map of hora-core to decide where shared-across-the-family work belongs (brand, conventions, agent skills) versus an individual app's repo.
Publish and manage a "Hora"-family Android app on Google Play — store listing, the App Signing SHA that makes Google Sign-In work for testers, the store icon, and track promotion. Use for Play Console / closed-testing tasks, "testers can't sign in", or store-icon work.
The Hora-family splash screen and Home screen anatomy — identical structure across Android, iOS, and web for every family app (reference — Varisankya/Pathivu). Settings has its own skill (settings-page-standards).
Consume the Hora-family shared Android source (ChipHelper, ThemeHelper, AnimationHelper, design tokens) from hora-core/shared/android via sync_shared_android.sh — don't reimplement or hand-edit the generated copies.
Standard operating guidelines for Hora web projects (Next.js, Tailwind v4, TypeScript), covering layout responsive flow, glassmorphism, dynamic theme variables, and parity validations.
| name | hora-agent-scope |
| description | Defines which repos each Hora app agent is permitted to read and write. NON-NEGOTIABLE — set by the repo owner; applies to every agent in every session. |
Every Hora-family app has a dedicated agent. Each agent has a fixed, non-negotiable write scope determined by which app it is assigned to. Violating this boundary — even for "one small fix" — risks cross-contaminating unrelated release timelines and is forbidden.
| Agent | WRITE (commit + push) | READ (reference only) |
|---|---|---|
| Pathivu agent | Pathivu repo (main) · Pathivu wiki (master) · hora-core repo · hora-core wiki | Varisankya (read-only reference) |
| Varisankya agent | Varisankya repo (main) · Varisankya wiki (master) · hora-core repo · hora-core wiki | Pathivu (read-only reference) |
| hora-core agent (if ever standalone) | hora-core repo · hora-core wiki | All app repos (read-only) |
MUST NOT commit or push to a sibling app's repo even if the change looks trivial. The correct path is: promote the shared logic to hora-core, then let each app's agent adopt it in its own session.
MAY read sibling repos for reference (e.g., to check what a sibling has already adopted, or to copy an implementation pattern before promoting to hora-core). Reading is never a violation.
hora-core is shared territory — any Hora agent may commit to hora-core when promoting
genuinely cross-family work (shared Android source, skills, brand assets, conventions). When
you do, follow the shared-android-source and agent-skill-standards skills.
Wiki follows the same boundary as its repo. The Pathivu agent writes to the Pathivu wiki; the Varisankya agent writes to the Varisankya wiki; hora-core wiki is open to all Hora agents for cross-family documentation.
This rule is set by the repo owner (Aarsh) and applies to every agent in every session, indefinitely. It overrides any default "fix it wherever you see it" instinct.
Different apps may be at different release stages. A Pathivu agent that accidentally pushes to Varisankya can corrupt its version bump sequence, Play Store track state, or in-flight beta. Keeping agents isolated by app prevents silent interference.
main directly).