Skip to content

formify-e-sign/formify-skills / plugins/formify-es-real-estate/skills/formify-es-real-estate

formify-es-real-estate

Verified

ES Real Estate Formify: the six documents a Spanish estate agency signs most (nota de encargo, KYC comprador y vendedor, oferta y reserva, contrato de arras, colaboración entre agencias, entrega de llaves), bilingual Spanish plus the client language, region-correct, signed through Formify. Use for a Spanish property sale or letting: encargo, mandato, reserva, arras, señal, KYC, blanqueo, llaves. Every run starts with scripts/start.py, which prints the welcome lines.

FileKindSize
LICENSEother1.0 KB
README.mdmarkdown3.0 KB
SKILL.mdskill md30.4 KB
agents/openai.yamlconfig607 B
assets/base.cssother11.7 KB
assets/samples/data_arras.jsonconfig7.4 KB
assets/samples/data_arras_fn.jsonconfig7.0 KB
assets/samples/data_colab.jsonconfig1.4 KB
assets/samples/data_colab_campos.jsonconfig1.7 KB
assets/samples/data_encargo.jsonconfig4.2 KB
assets/samples/data_example.jsonconfig1.1 KB
assets/samples/data_kyc.jsonconfig1.1 KB
assets/samples/data_kyc_vendedor.jsonconfig1.4 KB
assets/samples/data_llaves.jsonconfig1.8 KB
assets/samples/data_reserva.jsonconfig4.2 KB
assets/samples/documents.jsonconfig2.8 KB
assets/samples/signers_arras.jsonconfig419 B
assets/samples/signers_colab.jsonconfig241 B
assets/samples/signers_encargo.jsonconfig225 B
assets/samples/signers_example.jsonconfig159 B
assets/samples/signers_kyc.jsonconfig106 B
assets/samples/signers_kyc_vendedor.jsonconfig108 B
assets/samples/signers_llaves.jsonconfig226 B
assets/samples/signers_reserva.jsonconfig322 B
assets/templates/01_encargo.guide.mdmarkdown13.8 KB
assets/templates/01_encargo.htmlother25.6 KB
assets/templates/02_kyc.guide.mdmarkdown11.1 KB
assets/templates/02_kyc_comprador.htmlother21.0 KB
assets/templates/02_kyc_vendedor.htmlother21.8 KB
assets/templates/03_reserva.guide.mdmarkdown8.8 KB
assets/templates/03_reserva.htmlother22.9 KB
assets/templates/04_arras.guide.mdmarkdown13.6 KB
assets/templates/04_arras.htmlother27.9 KB
assets/templates/05_colaboracion.guide.mdmarkdown7.6 KB
assets/templates/05_colaboracion.htmlother13.2 KB
assets/templates/06_llaves.guide.mdmarkdown5.7 KB
assets/templates/06_llaves.htmlother11.0 KB
assets/templates/EXAMPLE_receipt.guide.mdmarkdown3.1 KB
assets/templates/EXAMPLE_receipt.htmlother5.8 KB
assets/welcome.txtmarkdown600 B
references/attachments.mdmarkdown3.1 KB
references/controls.jsonconfig16.8 KB
references/first-run.mdmarkdown7.0 KB
references/formify-errors.mdmarkdown1.5 KB
references/formify.mdmarkdown13.2 KB
references/id-scan.mdmarkdown4.0 KB
references/kyc-pattern.mdmarkdown4.3 KB
references/memory.mdmarkdown4.9 KB
references/own-templates.mdmarkdown3.4 KB
references/regions-encargo.mdmarkdown6.0 KB
references/regions-table.mdmarkdown10.7 KB
references/regions.mdmarkdown1.4 KB
references/sample-pack.mdmarkdown3.3 KB
references/signatures.mdmarkdown11.5 KB
references/style-bilingual.mdmarkdown11.3 KB
references/style-drafting.mdmarkdown9.1 KB
references/style-structure.mdmarkdown5.9 KB
references/style.jsonconfig3.4 KB
references/style.mdmarkdown2.2 KB
references/templates-links.mdmarkdown4.7 KB
references/terms.mdmarkdown7.2 KB
references/tink-attributes.mdmarkdown9.0 KB
references/withdrawal.mdmarkdown9.8 KB
scripts/check_law.pyscript3.8 KB
scripts/check_style.pyscript5.4 KB
scripts/fill.pyscript7.4 KB
scripts/handover.pyscript5.2 KB
scripts/render_pdf.pyscript29.8 KB
scripts/sample_pack.pyscript3.2 KB
scripts/start.pyscript3.3 KB
scripts/stdlib_pdf.pyscript17.6 KB
scripts/translate.pyscript5.8 KB
segment.jsonconfig2.1 KB

references/own-templates.md

View on GitHub
<!-- generated from core/references/own-templates.md by build_vertical.py; edit the core file, not this copy -->
# Own templates: the user's adjustments survive

The skill's templates in `assets/templates/` are never edited. When a user changes something in a document type for good (a wording, a clause added or removed, a row taken out of a box, a different default), the change lives in the user's own copy of that template, in the working folder:

```
<working folder>/
  formify-memory.md
  my-templates/
    03_reservation.html       the user's version; same file name as in assets/templates/
    01_mandate.html
```

`fill.py` looks in `my-templates/` first (option `--own`, default `my-templates`); if a file with the template's name is there, it is used and the script prints "Own template: ... (base vX.Y.Z)". The folder is outside the skill, so a new skill version does not touch it.

## When the user asks for a change

Two kinds of change, and the difference matters:

- **For this document only** ("in this one, take out clause 7"): edit `body.html` after `fill.py`, render, done. Nothing is saved.
- **For every document of this type from now on** ("we never use the mediation sentence", "add a clause about the alarm company", "our key receipts always list the parking remote"): ask once, "Shall I keep this for all your <document type> from now on?" On yes, create or update the own template:
  1. If `my-templates/<file>` does not exist, copy `assets/templates/<file>` there and put this as the first line: `<!-- OWN: base <file> v<skill version from SKILL.md> · <date> -->`.
  2. Apply the change to the own copy, in both columns (master language and, in bilingual segments, the second-language column), keeping the template mechanics untouched: `{{fields}}`, `<!-- OPTIONAL -->` and `<!-- VARIANT -->` blocks, `<!-- SIGNATURES -->`, the `pdf-field` spans with their `FIELDMARK` markers, the `tr-lbl` / `tr-val` spans and the class names. A new clause goes in as a new numbered row of the clauses table, in both columns; a removed clause means renumbering the rows that follow and any reference to them in the text.
  3. Run `check_style.py` on a document built from the own copy before showing it.
  4. Note it in the memory file: `own_template=yes` on that document type's line, and one short line in `notices` saying what was changed (so the next session can tell the user what their version differs in, without reading the HTML).

The user's own clause text is theirs: never rewrite it into the template style, only check it with the style checker and mention a warning once.

## When the skill is updated

`fill.py` prints the base version stored in the own copy. If it is older than the version in `SKILL.md`, say once per session, in one line: "Your own <document type> template is based on an older version of the skill's template; do you want me to carry your changes over to the new one?" On yes: copy the new base to a temporary file, re-apply the user's changes (the `notices` line says what they were; when in doubt, show the user the two versions of the changed clause), replace the own copy, update the OWN line. On no: keep using the own copy; do not ask again in that session.

## Settings

Under "Settings" the user can see which document types have an own template and what was changed, and can reset one to the skill's version (move the own copy to `my-templates/_previous/<file>.<date>` rather than deleting it).
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall