agentleFS
chanjalmechanjalme/claude-skills/skills/luno-os/SKILL.md

luno-os

Skill0 starsChanged 5 months agoMITView on GitHub

Use for ANY task touching Christian's Luno coconut beverage business: recipes, COGS/pricing, suppliers, branding, marketing, launch planning, permits, food safety, financials. Triggers on Luno, coconut drink, coconut beverage, latik, the stall, the launch checklist, GenSan coconut business, supplier/sourcing for the drinks. Loads the canonical Luno context from the Obsidian vault so numbers stay consistent instead of being re-derived each session.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use obsidian_search_notes for "Luno", "coconut", "Launch Checklist", "Recipes", "suppliers" to find the current versions.

    line 22
  2. Distinctive:

    Read the relevant vault note(s) before answering.

    line 25
  3. Distinctive:

    After a planning task, update the Launch Checklist (check items, add new ones) and append a one-line note to the vault activity log.

    line 27
  4. Distinctive:

    Keep it solo-operator and ₱22k-budget realistic.

    line 28
  5. Distinctive:

    Don't contradict locked financials without saying so explicitly.

    line 31
  6. Distinctive:

    Don't propose channels/tactics that need a physical stall before the online launch is done.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Luno OS

Single source of truth for the Luno coconut beverage venture. Always load the live vault notes first, then act. Never invent financials that contradict the vault.

Fixed context (stable facts)

  • Business: Luno Coconut Drinks. First-mover Thai-style coconut beverages in General Santos City.
  • Model: online-first launch, solo operator, ~₱22,000 startup budget.
  • Menu: 15 recipes. Signature topping is latik (coconut curds/drizzle), cost ₱2.50–₱3.60, sold as a +₱15 add-on.
  • Brand: butterfly logo system (variants: Psyche, MORPHO, IMAGO, Monarch, Mariposa).
  • Currency: PHP. Market: GenSan, UTC+8.

Canonical files (read these at task start)

Vault root: /Users/chanjalme/Documents/ClaudeProject/Obsedian/sample/smaple1

  • 10 - Projects/ — Luno project hub, Launch Checklist.md (16 sections, 200+ items), recipes, supplier list (27 suppliers), financials, inventory analysis.
  • Use obsidian_search_notes for "Luno", "coconut", "Launch Checklist", "Recipes", "suppliers" to find the current versions. Folder names contain intentional typos (Obsedian, smaple1) — do not rename.

Procedure

  1. Read the relevant vault note(s) before answering. Quote real numbers from them.
  2. For any COGS/pricing change, keep margins internally consistent and flag the impact (cost, sell price, margin %).
  3. After a planning task, update the Launch Checklist (check items, add new ones) and append a one-line note to the vault activity log.
  4. Keep it solo-operator and ₱22k-budget realistic. Reject advice that assumes staff or capital he doesn't have.

Guardrails

  • Don't contradict locked financials without saying so explicitly.
  • Don't propose channels/tactics that need a physical stall before the online launch is done.
  • Match Christian's plain style: no em dashes, no AI filler.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.