docopslab-dev 0.2.0 → 0.3.0

data/docs/agent/skills/asciidoc.md

@@ -1,436 +0,0 @@
-# AI Agent’s Guide to Writing in AsciiDoc
-
-This document is intended for AI agents operating within a DocOps Lab environment.
-
-Original sources for this document include:
-
-<!-- detect the origin url based on the slug (origin) -->
-- [Documentation Style Guide](/docs/asciidoc-styles/)
-
-If you learn nothing else form this guide, learn this: DocOps Lab is an AsciiDoc shop, and we _do not_ author in Markdown; we instead try to model excellent AsciiDoc authoring and syntax.
-
-Table of Contents
-
-- Avoid Slop Syntax
-- Automated Style Enforcement
-- General AsciiDoc Syntax Guidelines
-- DocOps Lab Specific Syntax Guidelines
-- Inline Syntax
-  - Inline Semantics
-  - Syntax Preferences
-- Block Syntax
-  - Block Semantics
-  - Use Delimited Blocks
-  - Example Blocks
-  - Attribute Formatting
-- Vale Configuration and Usage
-- Consumer Mode (Other Projects)
-
-## Avoid Slop Syntax
-
-The biggest mistake AI agents make when writing AsciiDoc syntax is that they slip into Markdown.
-
-**DO NOT use Markdown** syntax or conventions when generating AsciiDoc markup.
-
-Use AsciiDoc description-list markup instead of bulleted lists when topical or parameterized information is to be conveyed.
-
-DO use DLs
-
-```asciidoc
-some topic or term::
-The description of that term, possibly as a complete sentence or paragraph with a period.
-```
-
-DO NOT use arbitrarily formatted lists
-
-```asciidoc
-* *This kind of thing*: Followed by more information, is non-semantic.
-```
-
-Definition DO NOT do it in Markdown
-
-```markdown
-- **That awful double-asterisk notation** : Followed by a colon outside the bolding (no!) and then the "description". Just don't.
-```
-
-You will almost NEVER be asked to author in Markdown, except when leaving notes to yourself, in which case your unfortunate bias towards Markdown is acceptable.
-
-DocOps Lab is an AsciiDoc shop. With a few exceptions, all technical documentation is sourced in AsciiDoc format using a particular (standards-compliant) syntax style.
-
-Structured/reference documentation is typically stored in YAML-formatted files, often with AsciiDoc-formatted text blocks.
-
-Some documentation in DocOps Lab projects is written in Markdown format, such as documents intended for AI consumption (such as for agent orientation/instruction or for RAG retrieval).
-
-## Automated Style Enforcement
-
-DocOps Lab projects using the `docopslab-dev` tool automatically enforce documentation style guidelines. This is done using [**Vale**](https://vale.sh), a prose and source-syntax linter.
-
-To check documentation style:
-
-Check prose for style issues
-
-```
-bundle exec rake labdev:lint:text
-```
-
-Check for AsciiDoc markup syntax issues
-
-```
-bundle exec rake labdev:lint:adoc
-```
-
-Check both syntax markup _and_ prose
-
-```
-bundle exec rake labdev:lint:docs
-```
-
-DocOps Lab maintains a general-audience style guide in the AYL DocStack project repository and website. That guide is reproduced here.
-
-## General AsciiDoc Syntax Guidelines
-
-DocOps Lab documentation largely follows the conventions outlined in the [Recommended Practices](https://asciidoctor.org/docs/asciidoc-recommended-practices/) and[Writer’s Guide](https://asciidoctor.org/docs/asciidoc-writers-guide/) documents maintained by the Asciidoctor project.
-
-Reinforcements and exceptions:
-
-- Use `.adoc` extensions _execpt_ for Liquid templates used to render AsciiDoc files, which use `.asciidoc`.
-
-- Use one sentence per line formatting.
-
-- Use ATX-style titles and section headings.
-
-- For DRYness, use attributes for common URLs and paths (see Attribute Formatting).
-
-## DocOps Lab Specific Syntax Guidelines
-
-## Inline Syntax
-
-### Inline Semantics
-
-The main purpose of inline semantics is to provide a clear indication of the role of the text to the reader — including artificial readers.
-
-We can convey semantics by way of:
-
-- declaration by element, role, or class
-
-- text style based on declaration
-
-- browser effects based on declaration and additional data
-
-We use the following inline semantic coding in DocOps Lab publications.
-
-### Syntax Preferences
-
-Use inline semantics liberally, even if you only insert the heavier syntax on a second or third pass.
-
-Formatting with simple `*`, `_`, and ``` characters on first drafting makes lots of sense — or even missing some of these altogether until the second pass.
-
-But before you merge new text documents into your codebase, add role-based inline semantics wherever they are supported.
-
-Let the reader know and make use of special text, most importantly any **verbatim inline text**.
-
-Even if you are not ready to add such fine-grained tests to your pipeline, consider the value of having all your commands for a given runtime app labeled ahead of time (such as `.app-ruby`), and the advantage to the reader, as well.
-
-## Block Syntax
-
-### Block Semantics
-
-Use semantic indicators deliberately.
-
-The more you assert about a block of text you are writing, the better the placement and content of that block will be.
-
-Semantic assertions reside in the source markup, which may convey means of interpreting that same data visually in the output, as an indication to the reader.
-
-For instance, _warning_ admonitions should only deliver warning content, and the user should clearly see that a warning is interrupting the flow of the content in which it appears.
-
-```asciidoc
-[WARNING]
-====
-Avoid misusing or overusing admonition blocks.
-====
-```
-
-Semantic notations in our source remind us to treat the content properly.
-
-```asciidoc
-[WARNING]
-====
-Avoid misusing or overusing admonition blocks.
-This will be hypocritically violated throughout this guide.
-====
-```
-
-True as it may be, the second sentence in that admonition should be removed from the block. It can either be its own block, or it can be allowed to fade into the surrounding content.
-
-Sometimes the entire admonition may end up deserving this treatment.
-
-### Use Delimited Blocks
-
-Generally, use explicit boundary lines to wrap significant blocks, rather than relying on other syntax cues to establish the “type” of block is intended. These lines are called [_linewise delimiters_](https://docs.asciidoctor.org/asciidoc/latest/blocks/delimited/#linewise-delimiters).
-
-For example, use the following syntax to wrap the contents of an admonition block:
-
-Example 1. Example admonition block syntax with linewise delimiter
-
-```asciidoc
-[NOTE]
-====
-The content of an admonition block should be sandwiched between `====` lines.
-Use one-sentence-per-line even in admonitions.
-====
-```
-
-The standard linewise delimiters for various AsciiDoc blocks are as follows:
-
-<table>
-<tr>
-<td class="hdlist1">
-<code>====</code>
-</td>
-<td class="hdlist2">
-<p>For <em>admonitions</em> and <em>examples</em></p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code>----</code>
-</td>
-<td class="hdlist2">
-<p>For code listing (verbatim) blocks</p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code>....</code>
-</td>
-<td class="hdlist2">
-<p>For literal (verbatim) blocks</p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code> **** </code>
-</td>
-<td class="hdlist2">
-<p>For sidebar blocks</p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code>|===</code>
-</td>
-<td class="hdlist2">
-<p>For tables</p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code> ____ </code>
-</td>
-<td class="hdlist2">
-<p>For quote blocks</p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code>++++</code>
-</td>
-<td class="hdlist2">
-<p>For raw/passthrough blocks</p>
-</td>
-</tr>
-<tr>
-<td class="hdlist1">
-<code>--</code>
-</td>
-<td class="hdlist2">
-<p>For open blocks</p>
-</td>
-</tr>
-</table>
-
-For code listings, literals, or really any block that might contain text that could be confused with the delimiter, vary the length by using a greater number of delimiter characters on the _outer_ block.
-
-Example “example” block containing an admonition block
-
-```asciidoc
-[example]
-========
-[NOTE]
-====
-This is an example block containing an admonition block.
-====
-========
-```
-
-#### Exception: Brief admonitions
-
-Some blocks do not require delimiters. In cases of _repeated_, _nearly identical_ blocks, containing just one line of content, you can use the _single-line_ syntax where it is available.
-
-Example single-line admonition block syntax
-
-```asciidoc
-NOTE: This is a single-line admonition block.
-```
-
-<dl>
-<dt class="hdlist1">Exception to this exception</dt>
-<dd>
-We do not recommend the same-line syntax for admonition blocks other than `NOTE` and `TIP`. For `IMPORTANT`, `CAUTION`, and `WARNING`, use at least the 2-line syntax, if not explicit delimiters.
-
-```asciidoc
-[IMPORTANT]
-This is a critical notice, but it's not warning you of danger.
-```
-</dd>
-</dl>
-
-#### Exception: Single-line terminal commands
-
-Another common case is 1-line terminal commands, for which this guide recommends using a literal block with a `prompt` role added.
-
-```asciidoc
-[.prompt]
- echo "Hello, world!"
-```
-
-The single preceding space notation affirms the use of a literal block for any consecutive lines of content preceded by a single space. For multi-line terminal commands/output, use the `…​.` syntax to distinguish the block.
-
-#### Exception to the exceptions
-
-Whenever additional options must be set for a block, such as a title or role, use the linewise delimiter syntax — even in one-liner cases.
-
-```asciidoc
-[.prompt,subs="+attributes"]
-....
-echo "Hello, {what}!"
-....
-```
-
-### Example Blocks
-
-Use example blocks liberally. If something fits the description of being an example — especially if the words “example” or “sample” are used in the title, caption, or surrounding text referring to a given block of _anything_…​ then **wrap it in an example block**.
-
-Instances of the following block types may commonly be instances of examples, and just as commonly they may not be.
-
-- figures (diagrams, illustrations, screenshots)
-
-- tables
-
-- code listings
-
-- literal blocks (sample prompts, logs, etc)
-
-- rich-text snippets (rendered results, a user story, etc)
-
-Whenever any such instances _are examples_, prepend and append them with example blocks, and prefer to title them at the exampple-block level rather than the inner-content level.
-
-Example of a code block treated as an example
-
-```asciidoc
-:example-caption: Example
-
-.require statement in Ruby
-====
-[source,ruby]
-----
-require 'jekyll'
-----
-====
-```
-
-### Attribute Formatting
-
-AsciiDoc attributes are often used to store reusable matter. In certain contexts, attributes should follow a formatting convention that makes them easier to name and recall.
-
-For a complete guidance on attribute naming and usage, see [DocOps Lab AsciiDoc Attributes Naming and Usage](/docs/asciidoc-attributes/).
-
-#### URL Attributes
-
-Format URL-storing attributes like so:
-
-```asciidoc
-:syntax_area_descriptive-slug_form:
-```
-
-Where:
-
-- `syntax_` is one of
-
-- `area_` is a component or category like `docs_` or `pages_`, mainly to ensure unique slugs across divisions
-
-- `form` is the way the resource is presented:
-
-Examples
-
-```asciidoc
-:docopslab_src_www_url: https://github.com/DocOps
-:href_docopslab_aylstack_url: {docopslab_src_www_url}/aylstack/
-:href_docopslab_aylstack_link: link:{href_docopslab_aylstack_url}[AYL DocStack]
-```
-
-## Vale Configuration and Usage
-
-Vale configuration and styles are managed in coordination with the link:`docopslab-dev` gem.
-
-Our implementation of Vale allows for local project overrides while maintaining a centralized database of styles.
-
-Linting for documentation quality and consistency, both AsciiDoc markup syntax and prose quality/correctness.
-
-This tool provides a custom styles package and a modified configuration system, enabling multi-file merging.
-
-<dl>
-<dt class="hdlist1">Base config</dt>
-<dd>
-`.config/.vendor/docopslab/vale.ini` (from source)
-</dd>
-<dt class="hdlist1">Project config</dt>
-<dd>
-`.config/vale.local.ini` (inherits via `BasedOnStyles`)
-</dd>
-<dt class="hdlist1">Ephemeral config</dt>
-<dd>
-`.config/vale.ini` (merged from base and target)
-</dd>
-<dt class="hdlist1">Sync command</dt>
-<dd>
-`bundle exec rake labdev:sync:vale`
-</dd>
-</dl>
-
-## Consumer Mode (Other Projects)
-
-For all other projects, the gem works in a standard package consumption mode:
-
-- The project’s `vale.ini` should list all desired packages, including a URL to the stable, published `DocOpsLabStyles.zip`.
-
-- The `labdev:sync:styles` task simply runs `vale sync` in the proper context, downloading all listed packages into a local `.vale/styles` directory.
-
-> **TIP:** The `labdev:sync:vale` task updates both the base config and the style packages.
-
-A project’s `.config/vale.local.ini` should look something like the one for this repository (DocOps/lab).
-
-A snippet from DocOps/lab’s `.config/vale.local.ini`
-
-```ini
-MinAlertLevel = warning
-StylesPath = .vendor/vale/styles
-
-[asciidoctor]
-missing-attribute = drop
-safe = unsafe
-experimental = YES
-
-[_blog/*.adoc]
-DocOpsLab-AsciiDoc.ExplicitSectionIDs = NO
-
-[_docs/agent/**/*.adoc]
-DocOpsLab-AsciiDoc.ExplicitSectionIDs = NO
-DocOpsLab-AsciiDoc.ExtraLineBeforeLevel1 = NO
-```
-
-This dual-mode system provides a robust workflow for both developing and consuming the centralized Vale styles.
-
-> **NOTE:** For full Vale configuration settings (“keys”) reference, see the [official Vale documentation](https://vale.sh/docs/vale-ini).
-> **NOTE:** For information on managing DocOps Lab’s Vale styles, see [the `docopslab-dev` gem README](https://github.com/DocOps/lab/blob/main/gems/docopslab-dev/README.adoc).
-

data/docs/agent/skills/bash-cli-dev.md

@@ -1,135 +0,0 @@
-# Bash CLI Development for Agents
-
-This document is intended for AI agents operating within a DocOps Lab environment.
-
-> **TIP:** Use this guide in combination with the general Bash coding skill.
-
-Table of Contents
-
-- Bash CLIs
-  - Bash CLI Model
-- General CLI Principles
-  - When NOT to Use a CLI
-  - Semantic CLI Namespaces
-  - General CLI Conventions
-
-## Bash CLIs
-
-Bash scripts are often used for simple CLIs that wrap around more complex operations. Most repo-wide chores that do not require specialized Ruby-based tools like Asciidoctor or other gems are handled with Bash scripts (The significant exception to this are multi-repo libraries like the [DocOps Lab Devtool](/docs/lab-dev-setup/).)
-
-The one truly major Bash CLI we maintain is `docksh`, our Docker shell utility for launching properly configured containers for development, testing, and deployment (sourced in `box`).
-
-### Bash CLI Model
-
-Base CLIs are relatively open ended. Developers should consider how the script might change, but unless it is intended to be elaborate from the start, there is not much reason to fuss over complicated structures.
-
-> **TIP:** See [DocOps Lab Bash Coding Guide](/docs/bash-styles/) for details about implementing Bash CLIs.
-
-Let’s examine our typical Bash script CLI structure:
-
-```
-./bashscript.sh [arguments] [options]
-```
-
-If a Bash script is likely to eventually need to encompass multiple arguments or options, consider making it a Rake task and invoking Ruby scripts, instead.
-
-## General CLI Principles
-
-Most of our user-facing applications are Ruby gems, and most of those are intended to be used via three primary interfaces:
-
-1. An application specific, openly designed CLI utility.
-
-2. An application configuration file.
-
-3. Subject-matter content or domain-specific data of some kind.
-
-By way of these three interfaces, users can operate the application in a way that is optimized for their particular use case.
-
-CLIs should allow for runtime configuration overrides and even runtime content/data overrides. But most of all they should focus on conveniently putting power in users' hands.
-
-This means leaving the CLI model open to the task at hand, but it also means adhering to some conventions that apply generally to both Ruby and Bash CLIs.
-
-### When NOT to Use a CLI
-
-Even when an application offers a mature, well-designed CLI, there are times when either an application programming interface (API) or a domain-specific language (DSL) is preferable. Typically we want to keep complicated shell commands out of core products and CI/CD pipelines, in favor of native or RESTful APIs or else config-driven or DSL-driven utilities.
-
-### Semantic CLI Namespaces
-
-When designing CLIs, consider the namespaces of the elements we use: subcommands, arguments, and options/flags.
-
-Subcommands should be verbs or nouns that declare operations or contexts. At each position, these elements should be organizable into meaningful categories.
-
-Arguments should be meaningful nouns that represent the primary _subject or subjects_ of the command.
-
-### General CLI Conventions
-
-The definitive reference on CLI design is the [CLI Guidelines](https://clig.dev/) project.
-
-#### Option format
-
-<dl>
-<dt class="hdlist1">Use spaces rather than `=` to assign values to options.</dt>
-<dd>
-Flag forms such as `--option-name value` are preferred over `--option-name=value`.
-</dd>
-<dt class="hdlist1">Provide long- and short- form flag aliases for common options.</dt>
-<dd>
-For ex: `-h` and `--help`, `-c` and `--config`.
-</dd>
-<dt class="hdlist1">Use `--no-` prefix for negated boolean flags when applicable.</dt>
-<dd>
-For ex: `--no-cache` to disable caching.
-</dd>
-</dl>
-
-#### Command structure
-
-<dl>
-<dt class="hdlist1">Use subcommand only with apps that perform categorically diverse operations,</dt>
-<dd>
-Prefer flag combinations when possible. Subcommands signal a shift in execution context, and thus they can be greatly helpful when needed. Otherwise, reserve the first argument slot for something a meaningful arbitrary argument.
-
-A CLI with very handy subcommands
-
-```
-git fetch
-git commmit
-git merge
-```
-
-No subcommand needed
-
-```
-rhx 1.2.1 --config test-config.yml --mapping apis/jira.yml --verbose --fetch --yaml
-rhx 1.2.1 --config test-config.yml --html
-```
-
-And yes, of course you can combine fixed subcommands with arbitrary arguments.
-
-```
-git diff README.adoc
-```
-</dd>
-<dt class="hdlist1">Avoid using Unix-style argument structures.</dt>
-<dd>
-Arbitrary arguments should come _before_ options, even if that is counter-intuitive. Typically in our apps, users are modifying commands that get executed on the same target, so if the target is an arbitrary file path or version number, it should closely follow the command as an early argument.
-
-Preferred argument order
-
-```
-cliname targetfile --option1 value1 --option2 value2 --verbose --force
-```
-
-This structure lets users more conveniently change the parts of the command-line that will need more frequent changing.
-</dd>
-<dt class="hdlist1">Accommodate Unix-style CLIs by adding named options for every arbitrary argument supported.</dt>
-<dd>
-The trick is to enable those cases where the subject path or code _is_ what gets changed most often.
-
-```
-rhx --yaml --version 1.2.6
-rhx --yaml --version 1.3.1
-```
-</dd>
-</dl>
-