Centralize reusable FileMaker workspace guidance

skills/filemaker-naming/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: filemaker-naming
+description: Name or review FileMaker fields, variables, parameters, results, scripts, layouts, and related objects without weakening an established legacy convention. Use for new or changed FileMaker names, especially Boolean fields and variables.
+---
+
+# FileMaker Naming
+
+## Priority
+
+1. Preserve the consuming project's confirmed naming standard and existing legacy pattern.
+2. For a project that opts into an organization-specific standard, read that standard before proposing a name.
+3. Use these client-neutral defaults only where neither of the above decides the name.
+
+Do not rename existing objects solely to apply these defaults.
+
+## Boolean names
+
+Name a Boolean as a positive yes/no question:
+
+- `is...` for identity or current state, for example `isActive`
+- `has...` for possession or inclusion, for example `hasVendorAccess`
+- `can...` for permission or capability, for example `canOpen`
+- `should...` for intent or a business-rule decision, for example `shouldRetry`
+
+Avoid vague words such as `flag`, `status`, `check`, or `done`. Avoid negative names such as `isNotActive` or `hasNoAccess`; name the positive state and negate it in the logic where needed. Retain established FileMaker table-occurrence or scope prefixes.
+
+## Review before proposing a new name
+
+1. Search the current DDR and project sources for nearby names and scope prefixes.
+2. Keep an established family of fields or variables consistent.
+3. State the exact proposed name and why it fits the local convention.
+4. If evidence conflicts or the business meaning is unclear, ask a concise question instead of guessing.

skills/filemaker-naming/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "FileMaker Naming"
+  short_description: "Name FileMaker fields and variables clearly."
+  default_prompt: "Use $filemaker-naming to review names for new FileMaker fields and variables."

skills/ticket-delivery/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: ticket-delivery
+description: Prepare a concise project-manager reply and billable work report for reviewed FileMaker ticket work. Use when summarizing completed or reviewed work for a client, project manager, invoice, or handoff.
+---
+
+# FileMaker Ticket Delivery
+
+## Preconditions
+
+- Read the current ticket, relevant confirmed decisions, and the project's delivery rules.
+- For early analysis, label the response as a draft or return only the questions needed to continue.
+- Do not describe a proposal, an unverified assumption, or an open dependency as completed implementation.
+- Never send, post, or otherwise deliver the reply unless explicitly asked.
+
+## Project-manager reply
+
+- Lead with completed work, followed only by unresolved questions or confirmations needed.
+- Use concise, practical, client-facing English. Remove internal exploration and unused architecture proposals.
+- Distinguish completed work from proposed next steps.
+- When useful for verification, give a friendly label followed by the exact FileMaker object name in brackets, for example `Utility Switch [APPROVE::UtilitySwitch]`.
+- Include exact layout, script, custom function, or value-list names only when they materially help verification.
+- Include FileMaker code only when a calculation or script rule is central to approval. Put it at the end under a concise `KEY CALCULATIONS` or `KEY SCRIPT LOGIC` heading.
+
+## Short work report
+
+Create one only when the project requires it or the user requests it.
+
+- Maximum 450 characters, including title, bullets, and line breaks.
+- Start with the ticket number and a short title.
+- Use one to three short past-tense bullets describing completed work.
+- Exclude code, open questions, testing instructions, and unconfirmed claims.
+- Put the report in a fenced `text` block so it is easy to copy.

skills/ticket-delivery/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "FileMaker Ticket Delivery"
+  short_description: "Prepare concise FileMaker ticket replies and reports."
+  default_prompt: "Use $ticket-delivery to prepare a concise project-manager reply and work report."