sync: auto-sync from HOWARD-HOME at 2026-06-24 11:50:01
Author: Howard Enos Machine: HOWARD-HOME Timestamp: 2026-06-24 11:50:01
This commit is contained in:
@@ -89,6 +89,7 @@
|
||||
- [Calibrate effort to stakes](feedback_calibrate_effort_to_stakes.md) — Don't over-verify or over-engineer low-consequence details; confirm the happy path, note the limitation, and take the simplest path (e.g. put the instruction in the prompt) instead of building robust mechanisms.
|
||||
- [Pricing verification — no guessing](policy_pricing_verification.md) — ANY cost presented to the team or a client MUST be verified via live web lookup (WebFetch/WebSearch, fallback to headless Chrome). Never estimate from training data. Cite source + date inline. If unreachable, say so — do NOT substitute a guess.
|
||||
- [Client communication tone](feedback_client_tone.md) — How to write client-facing Syncro comments — expert partner, not intake questionnaire.
|
||||
- [Impeccable on outbound](feedback_impeccable_on_outbound.md) — Run the `impeccable` skill on anything sent to a client or vendor before delivery; internal drafts exempt.
|
||||
- [Default to inline links](feedback_inline_links.md) — Use `[text](url)` inline markdown links (clickable, wrap-safe) not bare URLs in code fences; exception = raw URL the user must copy/paste.
|
||||
- [Add Mike as owner on all Entra apps](feedback_entra_app_owner.md) — Apps created via management SP have no user owner — must add Mike manually or publisher verification fails.
|
||||
- [No TOML/config file approach for endpoints](feedback_no_toml_config_endpoints.md) — User explicitly prohibits TOML or config-file-based endpoint configuration — this will never be approved.
|
||||
|
||||
20
.claude/memory/feedback_impeccable_on_outbound.md
Normal file
20
.claude/memory/feedback_impeccable_on_outbound.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: feedback_impeccable_on_outbound
|
||||
description: Run the `impeccable` skill on any deliverable before it goes out to a client or vendor
|
||||
metadata:
|
||||
type: feedback
|
||||
---
|
||||
|
||||
Before sending ANYTHING to a client or another vendor — proposals, plans, reports,
|
||||
agendas, one-pagers, emails meant to represent ACG externally — run the **`impeccable`**
|
||||
skill on it first as a quality/polish gate. Applies to outbound, external-facing
|
||||
deliverables; internal prep docs and working notes do not require it.
|
||||
|
||||
**Why:** Mike wants everything that leaves ACG to be polished and on-brand. A rough
|
||||
internal draft is fine for us; a client/vendor never sees an unpolished artifact.
|
||||
|
||||
**How to apply:** When a deliverable is destined for a client/vendor, produce it, then
|
||||
invoke `impeccable` to audit/polish before delivery. For document deliverables, that
|
||||
means rendering them as a designed artifact (styled HTML/PDF one-pager) so `impeccable`
|
||||
(a frontend/UI design skill) can do its job — confirm the format with the user if unsure.
|
||||
Pairs with [[feedback_client_tone]] (tone) and [[stop-slop]] (text quality).
|
||||
Reference in New Issue
Block a user