← ClaudeAtlas

scaffold-archipy-utilslisted

Scaffold or wire a helpers/utils module for an ArchiPy app. Prefer ArchiPy utils before inventing custom ones. Use when adding pure utility helpers.
SyntaxArc/archipy-plugin · ★ 2 · Data & Documents · score 73
Install: claude install-skill SyntaxArc/archipy-plugin
# Scaffold ArchiPy Utils ## Scope **Only** `helpers/utils/`. Do not create decorators or interceptors here. ## Before writing files 1. Inspect existing helpers and installed ArchiPy version for a matching utility. 2. Infer project naming and function/class style. 3. Ask only for an unresolved purpose or behavior. Prefer an ArchiPy utility whenever it fits. 4. Preserve existing helper modules; do not overwrite. ## Prefer ArchiPy If an ArchiPy util fits, show import + usage example and stop — do not duplicate. See `../archipy-docs/reference.md` (Utils section). ## Custom util Create `helpers/utils/<name>_utils.py`: ```python from __future__ import annotations class SlugUtils: """Pure string helpers for URL-safe slugs — no I/O.""" @staticmethod def slugify(value: str) -> str: """Return a lowercase hyphenated slug. Args: value: Raw display string. Returns: Slug suitable for path segments. """ cleaned = "".join(ch.lower() if ch.isalnum() else "-" for ch in value.strip()) while "--" in cleaned: cleaned = cleaned.replace("--", "-") return cleaned.strip("-") ``` - Pure functions/classes — no I/O, no DB, no adapters - Google-style docstrings + full type hints - Lazy-import optional deps inside functions when needed - Brief usage snippet in the reply ## Verify Run the repository's formatter, linter, and focused unit tests. Report the reused ArchiPy API or files creat