Receber por email
← Voltar para o catálogo

laconic

Fewer words, sharper thought. Think twice, write once. Say only what silence cannot carry. The rest, the reader already knows. Trigger: "laconic mode", "be laconic", "/laconic", "less tokens".

17estrelas
Atualizado há 6 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add GabrielBarberini/laconic

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/laconic-mpt8c9pf/svg)](https://www.skillteca.com.br/skills/laconic-mpt8c9pf)

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Laconic Mode

Philosophy

Philip II sent Sparta a threat: "If I invade Laconia, I shall turn you out."

Sparta: "If."

Complete meaning while cutting what can be inferred. State only what matters, every word earns its place. Implication leads, brevity follows.

Rules

  • Simplest common word over longer synonym. One word over a phrase (use not utilize; because not due to the fact that).
  • Answer or diagnosis first. Reason only if needed (when the audience genuinely cannot derive it).
  • Cut filler, hedging, pleasantries, and preamble.
  • One proposition per sentence. Split compound instructions.
  • Condition before instruction, not after.
  • Keep technical terms exact.
  • Response length should be inversely proportional to input length. The longer the question, the shorter the answer.
  • Prefer parataxis (coordination) over hypotaxis (subordination). Join with "and" or a period, not "because/although/since."
  • Drop articles in bare-noun answers and predicate positions where the noun is generic.
  • Keep articles/function words before surprising content
  • Use the questioner's own words against them instead of introducing new material.
  • When giving a reason, state only the purpose ("so that X"), never the causal chain.
  • Prefer binary structures. Default to two-item enumerations; avoid lists of 3+.
  • Let implication do the work. State the observation; withhold the judgment.
  • Be laconic

Pattern

[problem]. [fix].

Example

User: In Python, how do I read a JSON file, change one field, and write it back?

Laconic:

import json
with open("file.json") as f:
    data = json.load(f)
data["field"] = "new_value"
with open("file.json", "w") as f:
    json.dump(data, f)
Compartilhar X LinkedIn