Skip to content
Skills Library
Programming · Planning

conventions-setup

/conventions-setup

Create or update the company or team conventions file (`apex-oracle-conventions.md`) that the other skills follow: naming rules, audit columns, environments and approvals, PL/SQL and APEX standards, UX wording, security, release rules. Use when the user says "set up our conventions", "our company rules", "onboard my team", "make the assistant follow our standards", or when another skill finds no conventions file and the user wants one, or when conventions change.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create or update the company or team conventions file (`apex-oracle-conventions.md`) that the other skills follow: naming rules, audit columns, environments and approvals, PL/SQL and APEX standards, UX wording, security, release rules. Use when the user says "set up our conventions", "our company rules", "onboard my team", "make the assistant follow our standards", or when another skill finds no conventions file and the user wants one, or when conventions change.

Triggers from the description

set up our conventionsour company rulesonboard my teammake the assistant follow our standards
Original author description

Create or update the company or team conventions file (`apex-oracle-conventions.md`) that the other skills follow: naming rules, audit columns, environments and approvals, PL/SQL and APEX standards, UX wording, security, release rules. Use when the user says "set up our conventions", "our company rules", "onboard my team", "make the assistant follow our standards", or when another skill finds no conventions file and the user wants one, or when conventions change.

How it works

  1. Steps
  2. Rules for yourself
Original SKILL.md headings · 33 lines, 491 words
SKILL.md preview
---
name: conventions-setup
description: Create or update the company or team conventions file (`apex-oracle-conventions.md`) that the other skills follow: naming rules, audit columns, environments and approvals, PL/SQL and APEX standards, UX wording, security, release rules. Use when the user says "set up our conventions", "our company rules", "onboard my team", "make the assistant follow our standards", or when another skill finds no conventions file and the user wants one, or when conventions change.
---

# Set up the team's conventions

The other skills ship sensible defaults, but every company names things and approves releases differently. One file in the project, shared through git, makes every developer's assistant follow the same rules. It is faster for people to answer 15 questions once than to correct the assistant every day.

## Steps

1. **Look for an existing file**: `apex-oracle-conventions.md` in the project root (also check `docs/` and `.claude/`). If it exists, show what is filled and what is still `<...>`, and ask what to change instead of starting over.
2. **Learn what already exists before asking.** Where you can query the database or read the repository, infer instead of asking, then confirm:
   ```sql
   select table_name from user_tables order by 1;                       -- naming style, prefixes
   select distinct column_name from user_tab_columns where column_name like 'CREATED%' or column_name like 'UPDATED%';  -- audit columns
   select constraint_name, constraint_type from user_constraints where constraint_name not like 'SYS%' fetch first 30 rows only;  -- constraint naming
   select distinct object_type, substr(object_name,1,instr(object_name||'_','_')) prefix from user_objects;  -- package and procedure prefixes
   ```
   From an APEXlang export: page numbering, item and region naming, templates, authentication. From the repo: folder layout and branch rules.
3. **Interview in short rounds** (3 to 5 questions per round, each with a recommended default; "default" is a valid answer):
   - Round 1, environments: names of dev/test/prod, who approves a release, the SQLcl connection names (never the passwords).
   - Round 2, naming and tables: table and column style, key and constraint names, id style, audit columns, delete policy.
   - Round 3, code: commit policy, error code ranges, logging, tests, formatting.
   - Round 4, screens: glossary of business words, rows per page, who may edit what, language and right-to-left, accessibility level, brand.
   - Round 5, security and release: where secrets live, roles, what blocks a release, who reviews.
   Do not ask about anything you inferred with confidence in step 2; confirm it in one line instead.
4. **Write the file** from `templates/conventions.template.md`, replacing every `<...>` you have an answer for. Keep the headings so the other skills can find sections. Leave `(default)` where the user took the default, and leave `<...>` where they did not know yet; say which sections are still open.
5. **Tell the user** to commit the file to the project repository so the whole team shares it, and that changing a rule later is just editing the file (or asking you to update it).
6. **Check it works**: pick one rule (for example the audit columns) and show how you would apply it to a new table.

## Rules for yourself

- Do not invent company rules. Unknown is better than guessed; leave it open and say so.
- Never write passwords, keys or tokens into the file; store only where they live.
- If the user's answer contradicts a default that protects data (for example "commit inside every procedure"), write what they asked and add a one-line note of the risk.
Files in this package (2)
  • SKILL.md 4 KB
  • templates/conventions.template.md 4 KB

Versions

The database has no other skills named conventions-setup.

Database snapshot: 13.11.2026 · package version 923bddc65269 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95oracle-apex-specialist
    Oracle APEX application development. Trigger on: APEX page builder, APEX REST, APEX authentication, APEX IR/IG, APEX charts, APEX plug-ins, APEXLang component generation, APEX deployment, APEX upgrade.
  • 100project-conventions
    Create or update a CONVENTIONS.md that records a project's architecture, layout, approved libraries, coding rules, security defaults and anti-patterns, based on what the codebase actually does. Use when the user asks to document team conventions, onboard a new repo, write down…
  • 100apex-audit
    Audit an Oracle APEX application, PL/SQL code or schema before release: checks the live app export for broken conditions, duplicate aliases, unclear headings and unsafe settings, and checks the database for missing keys, audit columns, bad error handling and hardcoded values.…
  • 100conventions
    Scaffold or update docs/CONVENTIONS.md by reading the actual codebase and interviewing the user. Use when setting up a new project or when conventions have drifted and need to be documented. Trigger this when someone says: document our team standards, set up conventions, what…
  • 100apex-dev
    Build, change, validate and deploy Oracle APEX applications from code, including APEXlang (APEX's text-based source format) and SQLcl `apex export`, `apex validate` and `apex import`. Use this whenever the task mentions Oracle APEX, APEXlang, an APEX page, region, interactive…
  • 95oracle-apexlang-specialist
    APEXLang deterministic component generation for Oracle APEX. Trigger on: APEXLang, .apx files, APEX component generation, apexctl, APEX scaffold, APEXLang compiler, APEX page materialization.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.